Tessera
Folgen

Ricky

@ricky.fm

React core team • Forbes 30 worst over 30

2545 Posts14273 Follower917 Folgt
dan@danabra.mov · last mo.

... i have joined the @nextjs.org team at @vercel.com. for a start, i'll be working part-time, so please don’t flood me with bug reports yet. however, i’ll try to keep an eye on them as i want to understand what problems Next.js users are running into every day. i want App Router to get good!

Max@maxwellcohen.bsky.social · 2mo ago

Very exciting Rust React Compiler news! @ricky.fm reports that the Rust port will be merged in the next week or two! Internal meta testing is showing 99.9% compatibility and much faster performance! github.com/facebook/rea...

[compiler] Port React Compiler to Rust by josephsavona · Pull Request #36173 · facebook/react

This is an experimental, work-in-progress port of React Compiler to Rust. Key points: Work-in-progress - we are sharing early, prior to testing internally at Meta, to get feedback from partners in...

github.com

Joe Savona@en-js.bsky.social · 5mo ago

We’re pretty close to having an initial Rust port of React Compiler. My approach was to iterate on the plan document (write it manually, have the agent expand, edit, repeat). Then try to run it, see what goes wrong, revert back to the plan, tweak the plan, repeat.

React@react.dev · 8mo ago

Researchers have found two new vulnerabilities in React Server Components while attempting to exploit the patches last week. These are new issues, separate from the critical CVE last week. The patch for React2Shell remains effective for the Remote Code Execution exploit.

Ryan Carniato@ryansolid.bsky.social · 9mo ago

People give `useEffect` a bad rap, but it isn't usually the source of the problem. The real problem is too many `useState`s. Devs fail to see how their data is connected and model it too discretely. As those connections appear, it is easier to synchronize than refactor the model. 1/

dan@danabra.mov · 9mo ago

aargh someone kill me. literally THE WHOLE POINT of directives is that they’re not just strings! they’re syntactically attached to the scope (function or module) in a way that’s reflected in AST. and both RSC and Next.js ones act at module boundary which is kinda gross for decorators or API calls

This event also led to various discussions in the community, following the introduction of parametrized directives (’use cache: private’ / ’use cache: remote’), and the introduction of a Vercel ’use workflow’ directive the next day. Many developers argue it’s dangerous to use strings and would prefer function decorators or explicit typesafe API calls. We still need to think about it before making up our minds and taking a side, but here are some related links worth checking out: