73 karma · joined May 26, 2016
[0] https://www.destroyallsoftware.com/talks/the-birth-and-death...
I'd say picking a platform is not, as it is definitely a critical part of your program, especially if it does not greatly increase the complexity of your code.
[0] https://en.wikipedia.org/wiki/Communicating_sequential_proce...
That has a nice, interactive visualization along with links to the paper itself, implementations, and talks about raft.
That being said, buffalo is getting pretty popular. http://gobuffalo.io/docs/getting-started
http://jvns.ca/blog/2016/10/02/i-just-want-to-run-a-containe...
https://commandcenter.blogspot.com/2012/06/less-is-exponenti...
The less magic that happens and the more code that is commonly used by all developers, the easier it is for others to read your code and understand what it does. Rob Pike and others have some interesting talks and blog posts on this
[0] https://prometheus.io/docs/introduction/overview/ [1] https://www.influxdata.com/products/
[0] https://commandcenter.blogspot.com/2012/06/less-is-exponenti...
https://commandcenter.blogspot.com/2012/06/less-is-exponenti...
I wouldn't say that it is inherently worse to have a simple feature set. Sometimes less is more [0]
[0] https://commandcenter.blogspot.de/2012/06/less-is-exponentia...
After that, the standard library is the best source for idiomatic go code.