3 ms·
“Why would you choose a motorbike over a hanglider or a catamaran?” Different technologies might all be able to get you to your destination, but some are going
by matthewmacleod 9y ago
“Why would you choose a motorbike over a hanglider or a catamaran?”
Different technologies might all be able to get you to your destination, but some are going to be more suited than others. This depends heavily or a wide variety of different factors. Large team or small team? High throughput or low throughout? Simple or complex?
The variables are too diverse to offer a meaningful answer. Use Rust when performance and safety are paramount. Use Go when you need to write a thin network-aware app or API. Use Node when you have an excess of JavaScript talent…
- tracker1 9y agoI came to say mostly the same... Rust is great for absolute control, and definitely in low-level scenarios (drivers, libraries, etc). Go is great for network services and alike. Where I find node shines is when it comes down to time to market, or orchestrating disparate platforms together. Node works great as a glue layer. Not that Go doesn't, but the amount of developer time to do it is quite a bit lower in Node imho, with a more agile approach. I'm a pretty big fan of web-facing applications talking to a service written with Node that will in turn talk to other systems behind it. It's probably the easiest place to transport that weirdly bound WS* service to something easier to consume in a different language. If/when performance is an issue, you have a working prototype for a Go rewrite. Most of the same network scaling issues apply to all of the above. And as an aside, all service authors should have to write a client in a static and dynamic language.