People have mixed feelings about the JavaScript ecosystem. Are we living in the JavaScript fatigue or in the JavaScript Renaissance? |
|
Daniel weighs whether designers or engineers should be responsible for pixel perfect design. To this point, at Elastic we’ve found that a highly effective approach is to maintain a design system — filled with React components and SCSS stylesheets — that’s kept on a tight leash by the design team itself, as a way of bridging the gap. |
|
“Web layouts can and most probably should morph as the viewport size changes. Our job is to make sure the layout is most effective in the space it has to perform in.” |
|
V8 has its own abstraction on top of assembly code: the CodeStubAssembler. The CSA allows V8 to quickly and reliably optimize JS features at a low level, all while supporting multiple platforms. |  |
|
Quokka is a rapid prototyping playground in your editor, with access to your project’s files, inline reporting, code coverage and rich output formatting. Community edition is free as in beer.  |  |
|
The latest in a glorious series on how JavaScript works, Alex dispenses wisdom in this deep dive about the networking layer of the web. |
|
Addy argues a little discipline can help if you’d like your site to load and be interactive quickly on mobile devices. |
|
Lara discusses how to bake accessibility into our design planning and development, instead of tacking it on as an after-thought. |  |
|
Here’s a weekly newsletter that digests last week’s security news into a shortlist of useful articles. |
|
A case study from Joshua on his experiments towards improving rendering performance in a React application — with an eye on slow networks. |  |
|
A compilation of React patterns, techniques, tips and tricks. |
|
At its core, a source map allows a browser to map compiled assets to the source code you use in development. But how does that happen? |
|
|
Comments