Even as a sighted individual, listening to conference talks at high speed is convenient (and you can still pause if you want to look deeper into something).
2,611 karma · joined December 12, 2012
[ my public key: https://keybase.io/wildpeaks; my proof: https://keybase.io/wildpeaks/sigs/yQmAnhmw5ODzOpfBpYvX1T7owc-Fwoe6TpMkU8-94Ho ]
Even as a sighted individual, listening to conference talks at high speed is convenient (and you can still pause if you want to look deeper into something).
Components can post messages to the worker to request an action on the state that will most likely change its data, but they can't edit the data directly, and props are only emitted if there is really a change in data.
Inside the worker, state is stored as immutable data, and action handlers are only allowed to make one non-async change (because the return value is the modified state). If it needs to do multiple things (e.g. download then process the result), it must schedule another action when it's ready to do the sync operation. This splits into granular easy-to-test operations on the state.
That way, it limits React (or Preact) to rendering (so it can also be used with other libraries, e.g. WebGL), and you can record the messages going through the worker to replay and analyze a scenario.
So far I'm happy with this setup, but I can understand the allure of thirdparty libraries instead.
For example, this happened recently:
User 1 kept having an issue, but no idea how to get debug infos.
User 2 had the issue once too and knows how to get debug infos, but can't reproduce the error.
By having both post in the same issue, the root cause and a matching solution were found before the maintainer even saw the issue :)
Tools help you get the job done, not get in the way.
"editor.fontFamily": "Fira Code"
"editor.fontLigatures": truehttps://github.com/google/guetzli/releases
and I'm getting "Invalid input JPEG file" from a lot of images unfortunately.
Their open source blog is also quite interesting: https://open.blogs.nytimes.com
However they can already be used in Node with the "--harmony-async-await" flag (and without flag in the upcoming Node 8).
Protractor (http://www.protractortest.org) is a good wrapper for Selenium: despite the name, you can totally use it with non-Angular pages (I'm a Preact person myself). It's convenient because it handles installing and updating webdrivers (which was especially handy on Windows), and seems well-maintained. And if you're using only Chrome and Firefox, it even has a direct connection mode to skip having to run a Selenium server (example: https://github.com/wildpeaks/threejs-examples-screenshots).
Otherwise if you just want to run tests in a real browser environment but don't want to test in multiple browsers, you could run them in NW.js, Electron, SlimerJS, or PhantomJS.