A lot of smart folks have been working on this proposal to bring native signals to JavaScript.

…Also I’ve been helping the smart people.

Have a look.

github.com/proposal-signa…

Today let's learn about four key primitives in SolidJS (signals, createAsync, server functions, and actions) brenelz.com/posts/learning…

This is a typical vinxi config for a SSRed Solid app. solid-start's actual config is not very far from this.

I just want to get a sense of how much of this makes sense intuitively. Feedback?

👀

Here's a new demo of Custom States that works in all browsers.

Chrome, Edge, Safari Tech Preview with CustomStateSet feature flag and Firefox 122 with dom.element.customstateset.enabled set to true.

Codepen link 👇

A concise example of why I really don't like decorators that much.

IMO, decorators should have been metadata only. We already have enough ways to duck-punch JavaScript into oblivion. 👊💥🦆

Ever wonder about how we got here? Tomorrow's stream I'm going to look at what's been going on the past several years in front-end web dev, and what that means for the future.
youtube.com/live/aA7Xeh7WG…

Jan-Niklas Wortmann Enea Jahollari 🅰 Mike Hartington In the currently released version of Chrome:

chrome://flags/ #observable -api

this is super exciting. the biggest blocker to adopting RSC with a non-framework setup is that it requires bundler support, and it’s *really hard* to write a plugin for bundlers that weren’t *designed* for a combined server/client module graph. first-class bundler support is huge

This is very important, so 👀. I’ve believed for a while that commoditizing end to end the setup, bundling utilities, low level primitives and consumption of RSCs is required for them succeed and actually grow beyond one of two routers on a single framework running on canaries.

YES PLEASE

RSCs have a very strong future if they can be used and adopted with much more minimal and customizable setups

Which means commoditize bundling and generalize routing

Can’t wait for Parcel, Vinxi, Turbopack, and hopefully Bun to make RSCs a first class citizen

Made some progress on supporting React Server Components in Parcel over the weekend. Will be very different from other implementations:

• Not a framework. No router, server, networking layer, cache, etc. — just the raw bundling primitives.
• Use with any server/router (eg…

I wonder when people will start talking about the difference between loading data in Server Components and Client Components. There are many benefits to using SCs to load data but it comes with tradeoffs. Having optimal SC fetching doesn't necessarily excuse poor CC fetching.

I built a thing last week: it’s a Scroll-Driven View Transition.

Yep, you read that right: the View Transition is controlled by you scrolling! There’s a lot to tell about this one, so let’s take a look …

there’s no denying that ai is changing how we work and’s finding its way into many of our workflows. that being said, there are things I WON’T use it for

new video up now (link in next tweet)

Want to read the entire code of Zustand v5-alpha? Here you go!

one step closer to acceptance 🥰

Form validation is hard. Especially with all the server stuff React is doing.

Here's a guide to help you do forms right!

Today's stream I'm going to continue the conversation on HTML partials and the complexity of state and view coordination across the server/client boundary.

youtube.com/live/N-QwFFqI8…

Ever wonder what makes Signals special or the difference in reactive systems?

It often lies in how state is derived.

'Derivations in Reactivity' by Ryan Carniato #webdev #javascript #reactivity #signals dev.to/this-is-learni…