3 ms·
I 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 s
by tracker1 9y ago
I 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.