Re:Goroutines, Nonblocking I/O, and Memory Usage
by dx034 on Friday January 06, 2017 @09:08AM
(#13336242)
The answer can always be "throw more servers/resources at it", and that's exactly why we end up with simple websites/programs reacting slower than their equivalent two decades ago. I have too many apps on my phone that don't work properly and take ages to load or perform simple tasks. I tried to report this for some apps, the answer usually is that my phone is too old or my internet too slow (I know not directly related to a server, but I guess developers wouldn't think differently there).
If you use a magnitude fewer resources, you can combine more services on one machine, ultimately allowing faster servicing and a better user experience.
And as I understand that's actually how many Go programmers think. If you don't care about resources, you can set up a simple server in Python. The beauty about Go is that it gives a good developer experience while still allowing to write efficient, optimized programs.
If you use a magnitude fewer resources, you can combine more services on one machine, ultimately allowing faster servicing and a better user experience.
And as I understand that's actually how many Go programmers think. If you don't care about resources, you can set up a simple server in Python. The beauty about Go is that it gives a good developer experience while still allowing to write efficient, optimized programs.