I think there's been quite a bit of interest to adopt Rust in production lately.
That might explain why Rust topics hit the front page so often.
That might explain why Rust topics hit the front page so often.
1. performance sensitive 2. want to run one stack across frontend/backend/native apps 3. don't want to learn multiple languages for multiple activities.
It's a pretty compelling pitch.
Horror!
JS isn't known for being great at encapsulation either, there could be some benefits for exceptionally large front-ends.
You get painless sharing of domain types between client and server via serde; you still get native async/await support; you get more powerful data modeling features than even Typescript can provide (although Typescript's union types are definitely much more ergonomic). You get a standard library that's not a joke. You don't have to wait until proposal-temporal gets ratified and implemented in order to have sane date/time handling (recently hit Stage 3 btw, woo!).
Honestly, only ScalaJS can match all of those benefits, as far as I can tell after examining a dozen of languages targeting the web.
So yeah, I'm super curious to hear what problems you encountered with Rust as a web frontend language.
meh. Doing tricky stuff with them is far easier as TS is a dynamic language, but the fact that enum variants are each a variant makes constructing them really easy:
let array = [1, 2, 3];
let some_array: Option<i32> = array.iter().map(Some).collect();