Anyone remember asm.js?
It allowed you to add "use asm" directives to functions and runtimes would compile them to binary. It was ahead of its time, but was criticized as forking JavaScript syntax and creating vendor lock in for Firefox.
It became WebAssembly.
It allowed you to add "use asm" directives to functions and runtimes would compile them to binary. It was ahead of its time, but was criticized as forking JavaScript syntax and creating vendor lock in for Firefox.
It became WebAssembly.
October 26, 2025 at 8:58 PM
Anyone remember asm.js?
It allowed you to add "use asm" directives to functions and runtimes would compile them to binary. It was ahead of its time, but was criticized as forking JavaScript syntax and creating vendor lock in for Firefox.
It became WebAssembly.
It allowed you to add "use asm" directives to functions and runtimes would compile them to binary. It was ahead of its time, but was criticized as forking JavaScript syntax and creating vendor lock in for Firefox.
It became WebAssembly.
I documented the initial process here, I seeded the WG with the React 18 members, and I think the best way to manage invites for now is to have a current WG member refer you be invited:
October 17, 2025 at 2:17 PM
I documented the initial process here, I seeded the WG with the React 18 members, and I think the best way to manage invites for now is to have a current WG member refer you be invited:
The same is true of React right now. Many of the new features feel worse than before because they're not integrated into the things you need to use them. But once they are, they will unlock better user experiences with less code than was possible before.
October 15, 2025 at 9:33 PM
The same is true of React right now. Many of the new features feel worse than before because they're not integrated into the things you need to use them. But once they are, they will unlock better user experiences with less code than was possible before.
It's going to take some time for libraries, frameworks, and apps to understand and implement these patterns. In a lot of ways we've taken a step backwards, so we can get even further.
But that's the way innovations work - they're never linear.
But that's the way innovations work - they're never linear.
October 15, 2025 at 9:28 PM
It's going to take some time for libraries, frameworks, and apps to understand and implement these patterns. In a lot of ways we've taken a step backwards, so we can get even further.
But that's the way innovations work - they're never linear.
But that's the way innovations work - they're never linear.
The ideal is no more than 3 paints:
- a busy state, local to the interaction
- a loading state for new pages
- the final content, animated in
- a busy state, local to the interaction
- a loading state for new pages
- the final content, animated in
October 15, 2025 at 9:21 PM
The ideal is no more than 3 paints:
- a busy state, local to the interaction
- a loading state for new pages
- the final content, animated in
- a busy state, local to the interaction
- a loading state for new pages
- the final content, animated in
yeah the time slicing demo was a classic. it's so good that everyone still talks about it, but it over shadowed the second half of the talk for the I/O benefits and the vision for "async react"
October 2, 2025 at 4:26 PM
yeah the time slicing demo was a classic. it's so good that everyone still talks about it, but it over shadowed the second half of the talk for the I/O benefits and the vision for "async react"
Finally, since this example is using Activity (stable today) and ViewTransition (stable soon), React animates to the result.
While that animation is in progress, React has nothing to do. So it does some more work on the hidden Activities, so they're ready to show next
While that animation is in progress, React has nothing to do. So it does some more work on the hidden Activities, so they're ready to show next
October 1, 2025 at 11:58 PM
Finally, since this example is using Activity (stable today) and ViewTransition (stable soon), React animates to the result.
While that animation is in progress, React has nothing to do. So it does some more work on the hidden Activities, so they're ready to show next
While that animation is in progress, React has nothing to do. So it does some more work on the hidden Activities, so they're ready to show next
After feedback is shown, React can begin working on the result of the click. It renders the DOM to and starts loading data. Then React commits it to the DOM and waits for things like images, fonts, or CSS to load:
October 1, 2025 at 11:58 PM
After feedback is shown, React can begin working on the result of the click. It renders the DOM to and starts loading data. Then React commits it to the DOM and waits for things like images, fonts, or CSS to load:
When a user clicks, React prioritizes the updates needed to show feedback for their click. Things like active button states, pending spinners, or optimistic state, all other updates wait for that to finish:
October 1, 2025 at 11:58 PM
When a user clicks, React prioritizes the updates needed to show feedback for their click. Things like active button states, pending spinners, or optimistic state, all other updates wait for that to finish:
is the desirable behavior here to paint every async request that comes in as fast as possible so there are flashes of intermediate frames? or are you thinking you'll add batching to defer a bit and limiting the number of paints at some point?
September 25, 2025 at 7:55 PM
is the desirable behavior here to paint every async request that comes in as fast as possible so there are flashes of intermediate frames? or are you thinking you'll add batching to defer a bit and limiting the number of paints at some point?
Are you specifically asking about how this directive for "use server" is used for defining a “sever component” which is meaningless since that directive is for sever functions?
September 23, 2025 at 9:43 PM
Are you specifically asking about how this directive for "use server" is used for defining a “sever component” which is meaningless since that directive is for sever functions?