Re:A Proposal for Package Versioning in Go
by ilovecars2 on Monday March 26, 2018 @03:41PM
(#16681806)
I have a hard time with using Java to write micro-services. Even though lots of packages, such as Undertow, support non blocking I/O, a lot of the rest of the stack and the programmers that use it don’t know how to do NIO. What happens then is that the SRE/Ops team needs to configure large thread pools which consume lots of RAM just because multiplexing is I/O so difficult.
In comparison I can just start goroutines and Elixir processes for fast and simple I/O parallelism almost without thinking about it.
Go has its good sides, but it's just a tool. It's not the best, because tools aren't supposed to be the best. Tools are supposed to be useful for what they're made for.