Colin van Eenige

Keep your HTML clean.

PHP had it right after all; we've come full circle.

Finding the right balance between precomputing and on-demand calculations can make a huge difference in user experience.

Spent time over the weekend building a menu component focused on accessibility and interaction. I still need to optimize the size, but it's currently under 1 kB. The details matter so much.

Working on what might be the best navigation I’ve ever built.

The best HTML framework? It's @astrodotbuild.

Plain JavaScript is underrated. We’ve grown so accustomed to abstractions, and for good reason, but sometimes the minimal solution is actually the better choice.

GitHub - AndreasMadsen/htmlparser-benchmark: Simple benchmark for diffrent htmlparsers using real-life data Simple benchmark for diffrent htmlparsers using real-life data - AndreasMadsen/htmlparser-benchmark

Trade-off in handling attributes during parse or on property access. During parse will push it to 0.4 ms/file. The attributes will only be parsed once regardless of how many times they are accessed.

Benchmark from github.com/AndreasMadse...

Working on the Astro Pipeline, which also turns out to be the fastest HTML parser out there. Query speed is not included in this benchmark, but it's also heavily optimized. Adding serialization for updates next.

Some might argue the optimization at this point, but I find it interesting to learn about performance and memory allocation for specific function calls, especially in iterations. Parsing HTML strings is a different beast.

Made an insanely fast HTML validator: benchmarked 10K nested nodes with attributes, parsing ~1.5ms, querying ~0.2ms. Almost perfect.

Noticed that in @astro.build v5.0, HTML boolean attributes now behave differently. Previously, you could use hidden="anything" and it would output as-is, but now it strips the "anything". Better for final output, inconvenient for processing.

Astro 5.0 | Astro Astro 5.0 brings exciting new features like the Astro Content Layer for seamless content loading from any source, and Server Islands for effortlessly combining static and dynamic personalized content.

Astro 5.0 is here.
Content layer, server islands, simplified prerendering, type-safe env, @vite.dev v6. All stable.

Go see what you can do 👇
astro.build/blog/astro-5/

Announcing Vite 6 Vite 6 Release Announcement

Vite 6.0 is out ⚡️
vite.dev/blog/announc...

The View Transitions API is one of the most exciting CSS features I've explored recently. Very powerful, but also complex.

50 followers to start with, looking for more previous connections that got quiet on the other platform. Used to share a lot about web performance, WebGL and CSS. Let’s connect again! 👋

Created a #threejs starter pack at go.bsky.app/2dqJYAt - share #threejs relevant content (with the hashtag) and ping me if you'd like to join it! Also if you'd like anyone to be in it, let me know! I added 30 ish to begin with, will grow it over time.

Yes, this was released initially one year ago and shared on 𝕏. Quite a few (performance) improvements pending, should I get back to it?

Here's webgl.app – Delivering satisfying visuals through patterns. Take a look and let me know what you think! ✨ #webgl #threejs

Web Performance Starter Pack! Who else is on here? ✍️

Ship less JavaScript.

I love writing CSS.