The browser has everything you need, why not everything needs to be server-rendered and how preloading can alleviate complexity. jovidecroock.com/blog/platform

From the thread: "Attacks from bot compromised Next.js assets spiked on 2025-12-05 from the usual 100 IP baseline to close to a 1000." If you're not 100% sure you're NOT vulnerable, you should patch your Next.js apps ASAP. And if you're 100% sure... patch anyway.

This is one of my favorite traditions that we do on Electron; it’s a great time to both recharge and get caught up on internal maintenance and projects that we might not normally have the time to look into

Disco is now 3x faster in Zensical 0.0.10! Comparing it to Lunr.js, used in Material for MkDocs, current results are: Indexing: 4x faster Querying: 20x (!) faster This means that Disco can handle much bigger indexes, e.g., 25 MB which roughly equals ~12.000 printed pages.

one downside of LLMs in OSS is _huge_ walls of text in issues, where the text does technically make sense but reads like a student trying to meet a character limit 😅

My most odd bug report: Enabling the @vuejs.org devtools extension breaks Strava github.com/vuejs/devtoo...

A couple of weeks ago at @perfnow.nl I gave a talk called "Fine-grained everything". It's about @svelte.dev (obviously), and the new frontiers of framework-land, but it's also about some stubborn misconceptions in web performance circles Gift link: conffab.com/presentation...

I want to explore making frameworks less "framework-y". I'm curious how far you could go in that direction. I want simpler things and less to worry about.

I'm totally not the target customer for this, but I keep coming back to this site just to marvel at how quickly it loads: www.mcmaster.com I wish more sites were like that.

Yesterday at TPAC I publicized my draft proposal for adding a declarative templating API to the DOM. github.com/justinfagnan... The repo has: 📖 Explainers for the templating API and DOM scheduler API 🏗️ Full prototype implementations ⚗️ a JSX transform ⚛️ a mini React-like framework

We have so many frameworks because we're trying to optimize for ease of development (locality of behavior), but the underlying platform is optimized for delivery.

Long overdue! This was super annoying and I could never figure out how to get back to a particular comment on a commit.

Hands down the best SSG and it's rust based. It's ridiculously fast!

Whenever I wrote something clever, it comes back to bite me in the end. Dumb and simple code always wins.

Neat lil learning from today’s @perfnow.nl (via Umar Hansa): You can now throttle individual requests in Chrome! Neat for experimenting with stuff like - lazy-loading: does the UI look okay if this chunk takes MUCH longer to arrive - resilience: what happens if this specific CDN is extremely slow

The estimated cost of legacy JavaScript = 37,000,000 trees. @inesakrap.bsky.social at #perfnow

Another source from my #PerfNow talk… Here’s why you need to know the performance plateau for your site. www.speedcurve.com/blog/web-per...

If you have an interest in understanding garbage collection better, or in how Go's new GC works under-the-hood, I highly recommend reading @michael.express's thorough guide through Go's current and Green Tea GC.

In the latest version of @rolldown.rs, JSON imports are tree-shaken! No more superfluous JSON values in your bundle, only these that you actually access. Without any change of code or config ✨ Interested in the code? Then check out the PR! github.com/rolldown/rol...

Wrote down some thoughts on the online vs offline tech discourse and building from first principles: marvinh.dev/blog/buildin...

Hierarchy of performance: HTML > CSS >>>>>>>> JS

Bundling is such an underused feature of server dev. It can easily reduce cold start times by 30-40%. Maybe it's because most backend deps are still stuck with commonjs.

web fragments are a pretty genius take on micro frontends. It's a problem most apps won't have, but for enterprise software with >1000 devs working on the same app this is huge!

A CSS terrain generator. No WebGL, just stacked grids and 3D transforms: terra.layoutit.com

v3 just released 🎉

Vitest 4 is out! - Browser Mode is Stable - Visual Regression Testing - Improved Debugging - Pool Stabilization - New APIs - Bug Fixes Stay updated with our blog post: vitest.dev/blog/vitest-4

I have a lot of respect for developers who don't mind removing their own code when a better solution emerges. Big kudos for that!

This blog post mirrors my impression of Rust code too. I often need to step through multiple abstractions or macros until you find the code that actually does something. daymare.net/blogs/everbo...

Signals flip the script. React renders where you create state. Signals render where you use state. Same state, but you are pushed into patterns that will lead to better performance by default. One paradigm shift away from memoization hell. 🎯 www.jovidecroock.com/blog/state-v...

added grouped updates to the preact signals devtools 🎉 thanks to @jovidecroock.com and the team for being open to early contributions 🙏

🎉 Preact 11 beta is here! After years of thoughtful development, we're delivering major improvements with minimal breaking changes. Better hydration, forward refs by default, and performance upgrades - all while maintaining the stability you love about Preact X.

I'm so glad that CSS is receiving so much attention in the browser space. It's amazing what you can do without any JS these days!

I dug into progressive image rendering and found a bunch of common assumptions aren't quite true. ➡️ JPEG & WebP progressive-renders worse in Safari ➡️ AVIF _does_ support progressive ➡️ But JPEG XL in Safari doesn't ➡️ JPEG XL decodes much slower than AVIF ⬇️ and more jakearchibald.com/2025/present...

Yup, spreading objects has always been slow. Same with for..of loops.

I love all the cool experiments that are popping up in my feed. The React model of putting everything into a component feels like it hindered progress. There are lots of cool explorations happening in every framework right now. 2026 will be an exciting year!

"Let's hear it for the UN of Javascript! Vite: The Documentary is finally here. If you missed the premiere, it's OK!!! Here's the link so you can watch it again, and again and again. youtu.be/bmWQqAKLgT4 "

As an experiment, we (the Firefox team) wanted to try a new way to get feedback on which Interop proposals matter most. So, here's a web app where you can rank the proposals you care about, giving us data we can use when reviewing which ones to champion. interop-rank.jakearchibald.com

I keep coming back to this one post in my draft folder that's more about the zen of coding, simple code, how it relates to performance, how performance is not exclusive to code and more stuff like that. I'm not sure if this is something that would be interesting to read about.

My favorite food place in my city just closed down :(

I hope that the upcoming full bundle mode in rolldown will allow us to ditch optimizeDeps in vite. Would make so many things simpler! I'm eagerly awaiting to give the full bundle mode a go once it's out.

This is such a good approach towards tracing of running applications! I always look forward to new go blog posts.

Making chains of middlewares type-safe seems to require a bit of dancing around with types. See github.com/microsoft/Ty...

Unwritten rule: Deep technical programming topics 🤝 Blog with barely any CSS

Not sure what's been happening to the NPM downloads of Preact but we've been going parabolic these past few weeks. I know that downloads don't indicate much but always fun to look at a project you've been working on for 7 years gain popularity npmtrends.com/@angular/cor...

I'm not sure if vite is ready for 2026. The internals seem to be tailored for SPAs whereas frameworks of today need more of a general purpose asset transformer across multiple environments. - no non-js modules - no dynamic entry points - constant plugin if(dev) branching - no ssr css modules

More boring software 👍

pnpm v10.16.0 adds "minimumReleaseAge", a setting for defining how long a version has to have been published before pnpm will install it. A nice countermeasure against accidental installs of short-lived compromised packages before they get taken down. Not a 100% fix, but a great additional step!

I feel like these days framework authors spend more time trying to get tools to work together rather than spending time in their framework. As great as tools are for end users, there's a pile of patchwork and hacks for framework authors :S I've been wrestling with vite issues all week...

The missing link in JavaScript tooling Some thoughts on the fractured nature of our tools how we could unify them all. I feel like this would remove many barriers framework devs run into. marvinh.dev/blog/unifyin...