7 ms·
Go is for distributed systems. It can be for system programming, depending on what you mean by system programming. I would personally not assimilate system pro
by user5994461 9y ago
Go is for distributed systems. It can be for system programming, depending on what you mean by system programming.
I would personally not assimilate system programming to embedded.
- axaxs 9y agoAnd even then, it's ok. Hell how many places has Java been embedded?
- sah2ed 9y agoPlenty. https://en.wikipedia.org/wiki/Java_Card https://en.wikipedia.org/wiki/Java_Card
- deleted 9y ago[deleted]
- user5994461 9y agoOr billions of places to talk in numbers. Java is running on so many smart cards, TV and set top box nowadays. It's almost everywhere.
- axaxs 9y agoI feel maybe my comment was misunderstood. I was saying that a GC doesn't disqualify a language from systems work, even embedded, using java as an example...
- camus2 9y ago> Go is for distributed systems Go is for distributed SERVERS.
- zzzcpan 9y agoYeah, Go is pretty bad at distributed systems programming, well, idiomatic Go. It can be tolerable if we throw away all those poorly designed idiomatic networking packages and multithreading. But it's definitely not for distributed systems. Its niche is more in boring servers and command-line apps where an interpreted language would be too slow, too memory hungry or harder to ship, where you can get away with only the simplest concurrency, but still prepared to deal with time-consuming concurrency bugs. Like a typical commercial CRUD app, a command line automation and data processing utility, a quick one-off program.
- user5994461 9y agoOr in simpler terms. Any server app where python/perl/ruby are too slow, and you can't use java/C#/C++ for some reasons.