now we need to port angular compiler to rust!
We should compile Firefox to wasm, and run Firefox inside Firefox so we can Rust while we Rust
Port React Compiler to Rust
31–40 of 128 posts
Re: Port React Compiler to Rust
#32Are people actually using the react compiler? Haven't heard about since ages ago when it was extremely slow
Yes absolutely. It's brilliant: all useMemo and useCallback can be removed and you get the same runtime performance and then some, at the cost of only a slight increase in code size. A small downside at the moment is the build time. This change will hopefully help address that because it will no longer depend on babel.
Very insightful, thanks. I just delved into it, starting here: https://react.dev/learn/react-compiler/introduction
Re: Port React Compiler to Rust
#33After bun [1] this is another high-profile project that was ported to Rust by extensively using LLMs.
Very curious to see how these rewrites play out. Is the LLM foundation solid enough to build upon and iterate on? Or does this cause projects to become unmaintainable because no person understands the implementation anymore?
Re: Port React Compiler to Rust
#34rewrite to rust using AI sound like meme now.
[dead]
Re: Port React Compiler to Rust
#35Re: Port React Compiler to Rust
#36rewrite to rust using AI sound like meme now.
Speaks volumes to the strengths of the language, also speaks volumes that LLMs lift the barrier of entry for Rust programming, the borrow checker woes can be offloaded to the model, you focus on all the other programming logic. Whats funny is I had been using Rust more with Claude because of this, and before Anthropic did their rewrite of Bun I tried a Rust rewrite of a C# project I had laying around (.NET 3.5 from b…
> LLMs lift the barrier of entry for Rust programming
I think you actually meant "lower the barrier" (which would make it easier to pass the barrier, while lifting it makes it harder)?
Re: Port React Compiler to Rust
#37now we need to port angular compiler to rust!
[deleted]
Re: Port React Compiler to Rust
#38Earlier quoted context omitted.
Speaks volumes to the strengths of the language, also speaks volumes that LLMs lift the barrier of entry for Rust programming, the borrow checker woes can be offloaded to the model, you focus on all the other programming logic. Whats funny is I had been using Rust more with Claude because of this, and before Anthropic did their rewrite of Bun I tried a Rust rewrite of a C# project I had laying around (.NET 3.5 from b…
> LLMs lift the barrier of entry for Rust programming I think you actually meant "lower the barrier" (which would make it easier to pass the barrier, while lifting it makes it harder)?
Lift the barrier as in remove it completely
Re: Port React Compiler to Rust
#39Shameless plug. I'm writing a TypeScript checker in Rust. It's not a port. I made this with a different architecture that hopefully once is done will be proven to be a better set of trade-off
Re: Port React Compiler to Rust
#40rewrite to rust using AI sound like meme now.
Speaks volumes to the strengths of the language, also speaks volumes that LLMs lift the barrier of entry for Rust programming, the borrow checker woes can be offloaded to the model, you focus on all the other programming logic. Whats funny is I had been using Rust more with Claude because of this, and before Anthropic did their rewrite of Bun I tried a Rust rewrite of a C# project I had laying around (.NET 3.5 from b…
> Speaks volumes to the strengths of the language
Memory safety is just a tiny part of over all security. If a LLM can transcode correctly, then it should also output 100% correct C code.
On the other hand, If a LLM cannot correctly transcode, then using Rust may just make the bug soundless, because the language runtime/code-gen "avoided" usual punishments that might make the bug (and bug report) obvious.