React Compiler is officially open-source! Check out the code: github.com/facebook/react…
And learn more at fb.me/react-compiler
Joe Savona
2,892 posts
- Some thoughts on the suspense changes from 19 RC. Most important: our bad. We got this one wrong, and we heard and sincerely appreciate your feedback. We'll hold the 19 release until we find a good fix.
- For compiler nerds: a writeup of the core inference rules and approach that React Compiler uses to decide which groups of instructions to memoize together. If something isn't clear let me know!
- As noted in RFC, frameworks such as Rails were one of many inspirations for React Server Components. We’re not swinging the pendulum fully to the server: we’re acknowledging that neither server- or client-rendering are ideal for all cases. Choose *per component* not per app.The pendulum is finally swinging back, and with the force of a wrecking ball. May the towers of needless complexity built in the past decade be smashed to smithereens 💥🔨
- 19rc1 is out with a new feature, sibling pre-rendering, that is the best of both behaviors. Amazing work by @acdlite and @sebmarkbage to implement this feature and @rickyfm, Jack Pope, and the rest of the team for verifying and rolling it out github.com/facebook/react…Some thoughts on the suspense changes from 19 RC. Most important: our bad. We got this one wrong, and we heard and sincerely appreciate your feedback. We'll hold the 19 release until we find a good fix.
- We’ve reached a fun milestone on React Forget: after months building the compiler itself, most of our work is now focused on product integration and experimentation. There’s still a long tail of syntax to support and optimizations that we’ll work on in parallel w experimentation
- We've made some exciting progress on React Compiler (prev called "Forget") — check out our latest labs post for more!Replying to @reactjsWe’re excited to share that React Compiler is no longer a research project: the compiler now powers instagram web in production and we’re working to ship the compiler across additional surfaces at Meta and prepare the first open source release.
- An early peak at the level of performance we’re targeting for React Native. We (React team at Meta) have been working closely w Hermes team on this from day one, it’s so exciting to see this coming together.We wanted to show the performance and the insane power of the Static Hermes native FFI. But we don't yet support the all language features needed to compile React Native (soon though!), so we improvised. We imported the bindings for DearImGui (a popular C++ imperative game UI
00:00 - I’m excited to share that we’re experimenting w porting Relay Compiler into #rustlang. Our early results are promising: w a bit of structure it’s easy to pick up, and we can move fast and ship high quality, efficient code.
- Replying to @o_kwasniewski @thymikee and @trozee_devBuilding an OSS cross-platform UI framework is incredibly challenging, even with corporate backing, and on the React team we have a ton of respect for Flutter. This post is an insult to all the hard work that’s gone into Flutter, which I’m sure will continue just fine.
- React is fundamentally a JavaScript library for UI. But a lot of folks actually want to use *typed* JavaScript with React - so we (React team) partnered with Flow to show what a typed JavaScript for React could look like. I’m really excited to see what ideas this inspires!We added new language features to Flow for writing React. Learn about our new Component Syntax: medium.com/flow-type/anno…
- One of the things I’m most proud of with React Compiler is the design of the HIR. For compiler nerds, it’s a mix of low-level CFG with high-level semantics, allowing us to do precise low-level analysis while producing compact, high-level output.
- The secret sauce of React is that you work with raw JavaScript values and your code directly defines the control flow of your UI. We take that last bit for granted, but not every library works this way.This Post is from an account that no longer exists. Learn more
- There’s a recent debate going on about whether it’s better to fetch data at the route level or the component level, with practical benefits cited for either. But people’s preferences are heavily informed by their architectural constraints. There’s no one right answer!
