TRPB

Wayland's approach to scaling sucks. It's broken by design. Sorry, devs, it just does.

If I set wayland display scaling to use 1.25 scaling it scales up to 2 then back down to 1.25. This makes everything apart from fonts (which are handled differently) blurry and has a bunch of annoying side effects.

1. Anything running in XWayland is scaled horridly and looks super blurry.

2. Any borders of UI elements or thin lines suddenly become blurry because 2 pixels can't go into 1 pixel so the scaling algorithm blurs the the nearest two to the average colour between them.

3. I can't view an entire 3840x2160 image in a web browser without scaling it down.

mrkwatz

As far as I am aware the time has come and as of Firefox 72 XUL has been stripped from firefox and so the method used to inject this scrollbar theme is no longer supported -- reference the following for future scroll themes:

Mozilla is currently working to phase out the APIs used to make this theme work. I will try to maintain each version until that time but eventually there will be no workaround. When that time comes there is a new, but more limited api for applying simple themes to scrollbars. In nightly I am currently using the following userContent.css

:root{
	scrollbar-width: thin;
	scrollbar-color: rgb(82, 82, 82) rgb(31, 31, 31);
}

jFransham

Achieving warp speed with Rust

Contents:

• Number one optimization tip: don't
• Never optimize blindly
• Don't bother optimizing one-time costs
• Improve your algorithms
• CPU architecture primer
• Keep as much as possible in cache
• Keep as much as possible in registers

samthor

// UPDATE: In 2023, you should probably stop using this! The narrow version of Safari that
// does not support `nomodule` is probably not being used anywhere. The code below is left
// for posterity.

/**
 * Safari 10.1 supports modules, but does not support the `nomodule` attribute - it will
 * load <script nomodule> anyway. This snippet solve this problem, but only for script
 * tags that load external code, e.g.: <script nomodule src="nomodule.js"></script>
 *
 * Again: this will **not** prevent inline script, e.g.:

joepie91

By the way, I'm available for tutoring and code review :)

Table of contents

1. What Promises library should I use?
2. How do I create a Promise myself?
3. How do I use new Promise?
4. How do I resolve a Promise?
5. But what if I want to resolve a synchronous result or error?
6. [But what if it's at the start of a chain, and I'm not in a .then callback yet?](https://gist.github.com/joepie91/4c3a10629a4263a522e3bc4839a28c83#6-but

ryanseddon

mocha --compilers js:babel/register,js:./test/css-modules-compiler.js --recursive -w

ddennedy

See my DASH-IF presentation from October, 2014:
https://s3.amazonaws.com/misc.meltymedia/dash-if-reveal/index.html#/

1. encode multiple bitrates with keyframe alignment:
   ffmpeg -i ~/Movies/5D2_Portrait.MOV -s 1280x720 -c:v libx264 -b:v 1450k -bf 2 \
     -g 90 -sc_threshold 0 -c:a aac -strict experimental -b:a 96k -ar 32000 out.mp4

   My input was 30 fps = 3000 ms. If it were 29.97, then a GOP size of 90 frames will yield a base segment
   size of 3003 milliseconds. You can make the segment size some multiple of this, e.g.: 6006, 9009, 12012.

cvrebert

Test apparatus: http://jsfiddle.net/hRub4/

(Windows = Windows 8.1 desktop)

• Windows Chrome 39
  • Button focuses on click and via keyboard tabbing
  • Anchor focuses on click and via keyboard tabbing
• Windows Firefox 30.0
  • Button focuses on click and via keyboard tabbing
  • Anchor focuses on click and via keyboard tabbing
• Windows Internet Explorer 11

staltz

The introduction to Reactive Programming you've been missing

(by @andrestaltz)

---

This tutorial as a series of videos

If you prefer to watch video tutorials with live-coding, then check out this series I recorded with the same contents as in this article: Egghead.io - Introduction to Reactive Programming.

---