News for hackers. Stuff that matters.
Re:Go best practices, six years in by Thaxll on Sunday May 01, 2016 @01:32PM (#11607025)
Go is pretty good for anything backend related.
Re:Go best practices, six years in by asimuvPR on Sunday May 01, 2016 @05:50PM (#11608019)
My experience over the years is that Go serves a specific niche ver well. The niche being boring long running services that do simple tasks in unison with other services. It's better to see it as a language wi th which you can build little self contained machines that work well together. I have a system made up of such little machines and it quietly works away at some low end server.
Re:Go best practices, six years in by eternalban on Sunday May 01, 2016 @03:03PM (#11607421)
No, that is definitely not correct, unless your "anything" is merely that which is fully defined & composed at compile time.

(And yes, you can go the IPC route to introduce dynamism that you get out of the box from a VM based language. But here is the classic case of the Go [tail] wagging the architecture [dog]..)

[edit: correct tail endian]