4 ms·
Rust isn’t versatile enough to be used in high-level contexts. You simply have to jump through too many hoops. It’s great for low-level apps but if I just want
by jimbob45 9mo ago
Rust isn’t versatile enough to be used in high-level contexts. You simply have to jump through too many hoops. It’s great for low-level apps but if I just want a simple UI and CRUD functionality, I’m reaching for C#/Kotlin.
That’s not a bad thing though. It’s okay to aim for your thing and be good at just that. No need to try to please everyone.
- esafak 9mo agoAnd Rust compilation is slow.
- noosphr 9mo agoI don't know why you are being downvoted. Rust in the Linux kernel is basically all unsafe which is what I expected to happen the first time I heard about it.
- ChadNauseam 9mo agoThat’s not my experience. I use rust in my web application. It’s compiled to WASM and runs in the browser. About as high level as it gets. And I almost never feel I have to jump through hoops. The only time I do is when I’m implementing something that’s plain impossible in javascript, like zero-copy deserialization. On the other hand, I constantly have to jump through hoops in javascript. You literally cannot compare two objects for structural equality in JS without jumping through hoops. It’s unbelievable. Yet no one says javascript is not versatile enough to be used in high level contexts. It is fair to say that the way Rust deals with closures requires too much hoop-jumping to make a truly ergonomic reach equivalent
- tharmas 9mo agoLeptos? Dioxus?
- ChadNauseam 9mo agoMeant to say "react equivalent". And no, I don't use either. IMO they're not quite mature enough for me to match my productivity in javascript with them. They're getting there though. I just use rust for the actually difficult logic and have javascript as a thin layer for the UI.