The Rust React Compiler is now native in Vite(blog.master.dev)

81 pointsby acusti4 hours ago5 comments

adzm3 hours ago
No more babel in my compilation pipeline, yay!
- Waterluvian21 minutes ago
  It’s just the best thing ever. Compiling at work took a minute for full builds with babel, and with rsbuild it now takes about 0.9 seconds.
- adzm40 minutes ago
  Update: changed a pet project to use this instead of the babel approach. Literally just did the config changes in the article, no issues. Time from `npm run dev` to ready went from 6 to 2 seconds.
syspec3 hours ago
Does this work with reacts fancy new compiler that is meant to optimize away various hooks?
- ownagefool3 hours ago
  If it wasn't obvious from the article, this is an implementation in the same thing in rust, ergo significantly faster. This was enabled, I presume, by the upstream react introducing code a rust version in source ( but they don't produce a standard binary last I checked )
Onavo28 minutes ago
Why does the Nextjs version of React compiler require a babel plugin when the vite version doesn't need it? Next.js is on SWC, not sure why they need a babel plugin.
prettycool3 hours ago
[dead]
glouwbug3 hours ago
[flagged]
- VertanaNinjai2 hours ago
  As funny as this is I sometimes wonder about that crowd. Assuming the ecosystem at large flips and most software is now written in Rust what will the “rewrite it in Rust” crowd move to? Will they be satisfied for the most part or does it morph into “now rewrite in $latest_rust”?
  - ablob2 hours ago
    I think the crowd will split into those who just cared about it being rust and those who wanted some kind of leverage to tempt others into doing something. The former crowd will cease being, while the latter looks for something new to push.
    I believe that one does not need to be overly concerned here. As with most things you will never satisfy zealots so it is sufficient to reconsider every once in a while when the status quo changed enough to warrant the effort (i.e. the actual arguments change).
    It is always a choice to participate in these "culture wars" or whatever you want to call this. If you can stick to a decision you can limit the impact quite a bit, I've come to realize.
    anpan hour ago
    I've never been someone to tell others to rewrite in Rust but I am a huge fan of the language and have in fact rewritten a lot of things in Rust. I'd be happy for another programming language to excite me as much as Rust has for the last 10 years, and then maybe I'd join that evangelism club instead :). Not sure how PL evolution is going to go in an era of coding agents though, very curious how that'll play out.
  - chmod7752 hours ago
    You will always have someone say "you should rewrite it in x", but it's rare that something carves out so much ground on the Pareto front you'll get a crowd.
  - steveklabnikan hour ago
    Because it became a meme virtually everyone who says this are actually joking and not serious.
    They'll move on to whatever the next meme is.
  - MBCook2 hours ago
    Maybe they’ll go back to “year of the Linux desktop”
  - wldcordeiro2 hours ago
    I think once you have it in Rust the next ask is using no "unsafe" code from that crowd.
  - dhbradshaw2 hours ago
    I'd argue for moonbit -- faster compile times, almost as fast, smaller wasm artifacts and like lean can have proof of correctness built in.
    Svoka6 minutes ago
    what the point? Rewriting in Rust is not just a language change. Rust enforces designing systems in secure way to start with, not just memory safety.
    For me last nail into becoming part of the crowd was Embassy. Whole my life I wrote some ad-hoc C microcontroller stuff. But just learning Embassy I realized that it could've been done much more elegantly and securely. If you have a spare moment, I would watch videos in this channel, old to new:
    https://www.youtube.com/@therustybits/videos