A Pipe Operator For JavaScript: Introduction And Use Cases
- Axel Rauschmayer tl;dr: "The proposal introduces a new operator. This operator is an idea borrowed from functional programming that makes applying functions more convenient in many cases. This post describes how the pipe operator works and what its use cases are (there are more than you might expect!)."featured in #287
The State of JavaScript Survey
tl;dr: "By collecting data from thousands of developers, the annual State of JavaScript survey is able to identify current and upcoming trends in the ecosystem."featured in #283
featured in #281
featured in #272
Understanding Why Our Build Got 15x Slower With Webpack 5
- Eoin Hennessy tl;dr: "We started, like we often do, with git bisect. It helped us track down the set of changes that appeared to have introduced the issue; adding a Dark Mode to Tines. "This is bizarre," we thought, "how could a bunch of CSS changes have slowed things down?"."featured in #271
The Invisible Javascript Backdoor
- Wolfgang Ettlinger tl;dr: "Unicode should be kept in mind when doing reviews of code from unknown or untrusted contributors. This is especially interesting for open source projects as they might receive contributions from developers that are effectively anonymous." Wolfgang highlights how invisible unicode characters are leveraged to breach security.featured in #268
We've Been Lied To: JavaScript Is Very Fast
- Jye Lewis tl;dr: "Modern JavaScript engines are incredibly fast at CPU bound tasks. To test the speed of modern engines, I wrote a small synthetic benchmark in C, then ported that same code to JavaScript to compare performance."featured in #261
featured in #260
Front-end JavaScript Performance
- Marc Radziwill tl;dr: In this post, Marc discusses the different types of JS performance issues, how to debug them, how to write fast front-end code and optimizing JavaScript code architecture.featured in #241
featured in #240