Port React Compiler to Rust
github.com
Port React Compiler to Rust
1–10 of 128 posts
Re: Port React Compiler to Rust
#2Curious but can we use lean4 as port target instead of Rust?
Re: Port React Compiler to Rust
#3Curious but can we use lean4 as port target instead of Rust?
I'm sure its technically possible, you might need to provide a bit more context if you expect anyone to change course here and port it to a programming language approximately no one has heard of rather than Rust though. What makes you think that would be a good idea?
Re: Port React Compiler to Rust
#4Are people actually using the react compiler?
Haven't heard about since ages ago when it was extremely slow
Re: Port React Compiler to Rust
#5What is the react compiler written in currently?
Re: Port React Compiler to Rust
#6I think it's fine to experiment, just communicate with your users and make sure its opt-in.
Seems like they kind of did that? The thread seems like people already were waiting on this, so that's positive.
Re: Port React Compiler to Rust
#7Curious but can we use lean4 as port target instead of Rust?
I'm sure its technically possible, you might need to provide a bit more context if you expect anyone to change course here and port it to a programming language approximately no one has heard of rather than Rust though. What makes you think that would be a good idea?
> approximately no one has heard of
Just cause it isn't used for webshit doesn't mean "approximately no one" has heard of it.
Lean is pretty much the most popular language mathematicians use today for computer-assisted proofs. More mature audiences may know about Rocq, Isabelle, etc., but Lean was already popular enough for a few people I know to have written their PhD theses on it about a decade ago.
I think GP is joking about a port to Lean because that would at least produce a formally verifiable output.
Re: Port React Compiler to Rust
#8What is the react compiler written in currently?
Uh, TypeScript?
Re: Port React Compiler to Rust
#9Why are they porting the Babel-isms? They should be using Oxc tooling directly, not hanging onto JavaScript parsers, IMHO -- isn't the benefit of porting to Rust that you can use fast native code?
It seems backwards that they are freezing the Babel AST into the interoperability contract and only using the more efficient native representations in an isolated fashion -- shouldn't it be the other way around?