I wouldn't think of Rust as a language for Front-end development or similar either, I rather think of it as a systems programming language. Yes, it may be able to imitate tools like React, but not replace them. Not even in the slightest.
Completely, I don’t see rust as a replacement for Scala, Java, Go (and especially) Javascript which tend to be what I use at work. It’s certainly possible, but I don’t think it would add much.
Rust is very much not aimed at web applications. You could say that it's aimed at _implementing web browsers_, and has become a general purpose language anyway.
In practice, I don't think Rust is really particularly well suited for this use case (especially the frontend stuff). But this is a really cool demo nonetheless, and the underlying WebAssembly will be something a lot of languages can use someday.
Yep, I don't think Rust is quite there yet for web dev. I didn't use Rust for any frontend interactions. The web app is an SPA written in Svelte. I only used it for the core state update logic, which benefits from the typing and performance boost.
Not exactly rust, but there's benefits to running the same language both on the front and back end. You could reuse template systems and validation logic for example.
I hate JS but replacing it with Rust for front end is a bad idea, Rust is a low level systems programming language, it's very suboptimal for high level front end code from productivity standpoint and it adds no value because it's advantages (mem safety with 0 cost abstractions) don't really matter in frontend (JS is super bad at being optimizable but it's still more than sufficiently fast).
I don't get the push for rust as a front-end language, it's very distracting with a lot of low-level features.
Can we just stick with "best tool for the job"?
Rust for performance-critical systems and, say, typescript for front-end? Using a single language for everything is a wet dream that always ends up in complexity and more work as you're fighting the "native" ecosystem.
I wondered about that - Rust looks like the one systems programming language I would actually enjoy using, but I don't know enough about it to have an informed opinion.
I'm really confused by what Rust has to offer to frontend. A systems language, sure. Memory safety when no garbage collection, fine. But we do have a garbage collector in the browser. And are expecting to get it for webassembly too. And when I compare Rust code to typescript, I want to howl in agony and ask, why would we inflict on ourselves this punishment. At least I can see the elegance and the beauty of Purescript, although I can't write anything useful in it. But Rust is just so horrendous for frontend, where the existing languages are so much nicer!
Agreed - I built a rust frontend framework, and tried to use it on the backend for a while. Ended up switching back to Python and Javascript for web - I use rust for embedded mostly now.
I don't think anyone uses Rust seriously for frontend work or backend unless they have a justified, specific use case; otherwise, currently, it is just a waste of resources and time.
Yeah with things like are we web yet, rust presents it self as can do anything language.
Which sure technically it can, but atm I think it's a only appropriate when you have an army of developers at some money printing company that go and write all your dependencies
reply