3 ms·
Which part? Compiling to .wasm? Java to me is "old reliable" but carries a lot of baggage and leaves a bad taste in my mouth to read/write. C#.NET I have less e
by smolder 6y ago
Which part? Compiling to .wasm? Java to me is "old reliable" but carries a lot of baggage and leaves a bad taste in my mouth to read/write. C#.NET I have less experience with. Neither can quite match Rust for cpu/memory efficiency, but they definitely have their place being capable, accessible, and efficient languages with robust "ecosystems".
- pjmlp 6y agoAll of them, native code, wasm, whatever. Yes, they might not match Rust down to the microsecond or byte count, it doesn't matter in distributed computing. There are bigger fishes to fry as distributed computing problems. And Rust type system for preventing data races among threads doesn't help when what is being used is distributed IPC across a cluster nodes.
- smolder 6y agoI understand where you're coming from. I hear the "bigger fish to fry" sentiment often. The point about distributed data races is a good one. At one point I did a comparison between a mono/Nancy web service and the same web service, feature for feature, built in NodeJS, Rust/rocket, and Go. I built a few different endpoints that did different types of work and load tested them, profiled memory usage, etc. I know mono and perhaps Nancy weren't the best point of comparison, and it's been some time since, but Rust/rocket really impressed me then, including on axes like ease of development and code readability. The perf deltas I saw could matter quite a bit at scale, allowing for fewer/cheaper servers. I've enjoyed using Rust for a few things since, personally, and am so far pretty unbothered by its shortcomings.