RSCs were a mistake. I went back to a client-side only solution using Preact for my latest project because the complexity you buy into is simply not worth the benefit of RSCs.

this is nuts, non-dismissible full page message, social meta title swapped to CVE-2025-55182

I actually love this disclaimer

On a totally different subject, Belgium has increased VAT on gym membership and other sport related stuff. All while we know that exercise increases lifespan and logically extends to that reducing social security costs as people are healthier... Anything to increase taxes I guess...

To put this out there, last week I've stepped down as a maintainer of GraphQL-JS. I've decided for myself that I spend a lot of time on OSS and I want to spend that time on projects where I can feel impactful. I wish my fellow ex-maintainers on the project the best of luck!

have been using preact for a side project recently and am thoroughly enjoying it the signals dev tools are super nice too. would love to see similar exist for other frameworks, even just to visualise the signal networks/flows

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 😅

Never thought I'd experience the low of talking to a user, I mean LLM... For an entire issue. This is just beyond hopeless and a lot of my interactions have devolved into this... github.com/preactjs/sig...

My favorite AI benchmark nowadays is to take a semi-complex bug from the Preact/Signals repository (or an intersection thereof) and ask it to write a failing test. Thus far I haven't been replaced as an OSS maintainer, not even by Gemini 3

If taxing billionaires won’t work then taxing us won’t either, right?

I've felt a tendency of issues to be AI authored lately, they overly bear the frustration of the user pretty frequently and the reproductions are inaccurate a lot of the time. Has anyone else noticed this?

Vibe coding PRs - STOP please...

Well, the last two months of 2025 are there and... I haven't published anything but open-source stuff.... Surely 2026 will be the year... Right? Right?

Open source never stops: graphql-js v16.12.0 was just released 🚀 @jovidecroock.com is bringing the latest spec addition to the stable branch, such as operation descriptions and schema coordinates. Check it out 👇 github.com/graphql/gra...

Here's a toy app using @preactjs.com + signals and @nitro.build (to avoid the browser's CORS error) It's an example on one of the ways you can use signals and how most of the App logic can be changed to just listening to values as compared to dealing with hooks 1/n

I think I found a chromium bug - when using moveBefore on a focussed input where you have a selection range it loses its selection range. Chrome bug: issues.chromium.org/issues/45482...

I forgot the golden rule of "Don't read the comments if someone posts your article to Hackernews and it hits frontpage"....

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...

got laid off due to restructuring :( i’m now available for mid+ frontend developer/software engineering positions in the meantime, we’re back to building the future and fun on the web on atproto :)

”We fed our horse and a competing jet engine hay for a week and then measured their hooves. The results will astound you.” Web dev discourse in 2025.

We were the AI of the Neanderthals

I, as a person, am one big memory leak

The 3 worst GraphQL myths: ❌ Everything is POST ❌ All URLs are /graphql ❌ Anyone can query anything One solution destroys all three: Persisted Operations/Trusted documents www.jovidecroock.com/blog/graphql...

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!

GraphQL should be an implementation detail

Also doubles as a visualization of how Preact Signals work!

Anyone know a way to see overall open-source engagement within i.e. a programming language or a GitHub topic? I've been curious as it looks like engagement has dropped (PR/issue creation) while usage has gone up

Signals change the paradigm from, rerender where you create state to rerender where you use state. It requires a different mindset but ultimately these are free performance gains

i think migrating away from Vercel hosting is a solid idea. i moved my Next.js blog to Cloudflare (for free) and have been very happy with that with Next.js 16+ committing to deployment adapters (and Vercel adapter using the same API), we should hold their feet to the fire on the ease of migration

There’s never been a better time to switch from Next.js to Astro nitter.net/rauchg/statu...

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...

Seeing the impact of my performance efforts in the wild really makes my day github.com/captbaritone...

This was a very good read. It's also a good reminder to check our own NPM access token pages and maybe delete old lingering tokens.

I've really had it with AI generated issues and tests, most can't even take the time to read that their test is actually asserting anything. I've just received a PR that asserted nothing - assert(true).tobe(false) - and didn't bother to look at how our tests are structured... OSS being great lately

Growing as a person means using signals... I don’t make the rules @ryansolid.bsky.social does

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...

Signals transform the paradigm from, re-calculate where you create state to re-calculate where you access state.

Can we collectively agree, and maybe point out, that this is not okay... If a code gets compromised then for that short time window it should be able to do none or limited damage. Anyone with good contacts at npm?

Seems that NPM too allows TOTP reuse within the time-step window. Seen a similar issue in multiple services over the years. Per RFC 6238, a TOTP (Time-based One-Time Password) should be single-use. Allowing reuse, even within the short-ish time window, is not ideal (shoulder surfing, phishing etc.)

NPM supports switching from Authenticator App (TOTP) based 2FA to more phishing resistant WebAuthn based 2FA. Adding a WebAuthn security key and disabling the Authenticator App is a pretty quick process. For example Apple Touch ID & Windows Hello work! Physical keys work too, but aren't required.

Celebrating the contributions of our amazing community at #GraphQLConf - thank you to our 2025 GraphQL Stars!

Fresh 2 has graduated to beta releases - essentially release candidates before a stable release. Fresh can now act as a Vite plugin, opening the door to HMR, faster boot times, and Cloudflare deployments. deno.com/blog/fresh-a...

I wish I had more time to be involved with JS tooling. There is so much room for improvement there that would push everything forward.

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

Being honest, this has been one of the most humbling experiences. I often feel like I need guidance to do my best work and this has been largely steered by our community and a vision I had. This has felt like a real achievement for me, thank you to whoever tries out the beta!

🎉 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 wonder if an LLM will ever write a GraphQL Parser in TypeScript types thinking it won't be an absolute pain.

I love building developer tools but lately as I was reflecting it daunted on me that the impact my work has had is hard or even impossible to measure. Have people had more fun building or made higher quality things due to my work on preact/gql.tada/urql/...?

JS isn’t slow, your code is. the way we disregard performance and exepect to be fast is one of our biggest problems.

devs will be like "why's TypeScript so slow, I don't have that much code" and then at the top of their code it's import React from "react"; import db from "some-huge-database-schema"; import * as Icons from "library-with-10000-icons-reexported"; import gh from "the-entire-fking-github-api-graphql";