3 ms·
Why wouldn't you just use OCaml, Haskell, F#, or Scala, where you've got much more mature web framework options? Don't get me wrong, Rust is fine, but if you do
by lmm 6y ago
Why wouldn't you just use OCaml, Haskell, F#, or Scala, where you've got much more mature web framework options? Don't get me wrong, Rust is fine, but if you don't need its memory management then why make trouble for yourself?
- deleted 6y ago[deleted]
- riquito 6y agoIt's in the preface > The project is simple enough that I can't imagine being too limited by any language's ecosystem. And I've been itching to write something substansive [sic] in Rust...
- vghaisas 6y agoI think it's also a bit of a chicken and egg problem: If no one uses Rust for web servers then its ecosystem won't ever mature. If there are people willing to deal with some rough edges, that's great and will help the ecosystem mature.
- Lio 6y agoRust is interesting in that it may eventually end up as a very useful language for WASM work. Rust has the advantage that when compiled to WASM it won't require a runtime library. So the prospect of Rust as a fast, low overhead, use anywhere language is tempting. Since Rust is a relatively new language it's worth checking to see how it's maturing over time against small low risk projects exactly as the author has done. Rust may not be a perfect fit right now but that may change. So it's very valid to test one's assumptions from time to time. Or to put it another way, working in one of the languages you've mentioned wouldn't answer the question "how suitable is Rust for web server work right now?"
- jfkebwjsbx 6y agoAll that applies to several other very mature languages that can target WASM, like C. Nevertheless, WASM is not ideal for server work. It is intended for the frontend.
- Lio 6y agoSorry, I may not have explained my point clearly enough. I'm not suggesting that you would use WASM for server work at all. I'm suggesting that Rust would be interesting for WASM on the frontend because it doesn't depend on a runtime. Given that you might want to use Rust for WASM you may also want to use it on the backend (that's without using WASM on the backend). The assessment of Rust via small projects says nothing about the suitability or not of C or any other language. It's just about the suitability of Rust right now and how it's changed from the last time you assessed it.
- jfkebwjsbx 6y agoFair enough. I wanted to mention that Rust is not the only language that targets WASM since you talked about maturity.
- estebank 6y agoI am really looking forward to WASM as the technology of choice for language agnostic performant plugins. That is a backend niche.
- jfkebwjsbx 6y agoDynamic linking has been a thing for 50 years. No need for WASM for that.
- estebank 6y agoDynamic linking provides no process isolation or higher level constructs through the ffi boundary.
- jfkebwjsbx 6y agoBinary interfaces with process isolation have existed for at least 30 years, too.
- voxl 6y agoIf you don't need its memory management then why would you use a garbage collected language and lose the performance gain?