/JavaScript

Coding My Handwriting

- Amy Goodchild tl;dr: Amy created a cursive version of her coded handwriting by defining key points for each letter, smoothing paths, and implementing custom joining logic. She describes her approach. 

featured in #516


The Self-Rendering Eval Shirt

- Eric Simons tl;dr: The free t-shirts companies give away to developers are everywhere and, with a few exceptions, most are pretty boring: usually just a logo on a t-shirt. In this post, see how StackBlitz’s co-founder broke this mold with a t-shirt design that incorporated the StackBlitz logo constructed with \*actually valid\* JavaScript code that is the source code of the image itself.

featured in #496


JavaScript Bloat In 2024

- Nikita Prokopov tl;dr: “I was a bit out of touch with modern front-end development. I also remembered articles about web bloat, how the average web page size was approaching several megabytes! So all this time I was living under impression that, for example, if the average web page size is 3 MB, then JavaScript bundle should be around 1 MB. Surely content should still take the majority, no? Well, the only way to find out is to fuck around. Let’s do a reality check!”

featured in #492


The Self-Rendering Eval Shirt

- Eric Simons tl;dr: The free t-shirts companies give away to developers are everywhere and, with a few exceptions, most are pretty boring: usually just a logo on a t-shirt. In this post, see how StackBlitz’s co-founder broke this mold with a t-shirt design that incorporated the StackBlitz logo constructed with \*actually valid\* JavaScript code that is the source code of the image itself.

featured in #491


2023 JavaScript Rising Stars

- Michael Rambeau tl;dr: "Welcome to the 8th edition of the JavaScript Rising Stars, the place to see the trends about the JS ecosystem in 2023. Let's see how a set of UI components you copy-paste took the world by storm!"

featured in #478


How We Reduced The Size Of Our JavaScript Bundles By 33%

- Umair Nadeem Rich Hong tl;dr: Dropbox reduced its JavaScript bundles by 33% by replacing its outdated module bundler with Rollup. The existing system led to large bundle sizes and performance issues. Rollup's features like automatic code-splitting and tree shaking optimized the bundling process. Despite challenges in implementation, the transition to Rollup significantly improved performance.

featured in #441


Shrinking VS Code With Name Mangling

- Matt Bierner tl;dr: The Visual Studio Code team reduced the shipped JS size by 20% without major refactorings or code deletions. They introduced a new build step called "name mangling" to automatically shorten long identifier names in the codebase. Initially, they tried mangling private properties, but due to potential complications, they turned to mangling exported symbol names instead.

featured in #435


Writing Javascript Without A Build System

- Julia Evans tl;dr: “I want to talk about what’s appealing to me about build systems, why I still don’t use them, and why I find it frustrating that some frontend Javascript libraries require that you use a build system.”

featured in #410


Writing Javascript Without A Build System

- Julia Evans tl;dr: “I want to talk about what’s appealing to me about build systems, why I usually still don’t use them, and why I find it frustrating that some frontend Javascript libraries require that you use a build system. I’m writing this because most of the writing I see about JS assumes that you’re using a build system, and it can be hard to navigate for folks like me who write very simple small Javascript projects that don’t require a build system.”

featured in #391


State Of JS 2022

- Sacha Greif Eric Burel Sarah Drasner tl;dr: "We saw a continuation of performance-lead innovations, many in reactivity and hydration (or the lack thereof). For example, Svelte took on simplicity in developer ergonomics and leaned into the compiler. Solid’s explored new approaches to reactivity, while Qwik shifted our mental model with resumability."  

featured in #381