Writing web applications using only the Go Standard Library
Look, I'm a big fan of go; I like the language, I (mostly) like the community, and I've seen some excellent stuff built in it.<p>...but, this 'dont use anything but the standard library' movement that keeps popping up here and on reddit is just ridiculous.<p>It's just fall out from people who can't <i>be bothered</i> figuring out how to use 3rd party dependencies.<p>No matter how amazing and excellent your language development team is, the man power of work in the wider ecosystem is significantly larger, and avoiding the work done by others to 'hand roll' your own solution is not the answer.<p>Yes; learning frameworks is tedious.<p>Yes... sometimes someone elses 'style' of code might not match yours...<p>...but, you have to ask yourself: are you writing code as an intellectual exercise, or trying to build something?<p>Because, if you're trying to build something, and you want to write every little piece of it yourself; you'll never build it.<p>This is the same (daft) argument as people suggesting they build their own game engines.<p>Building websites isn't trivial; and there are parts you need to do it aren't in the standard library, and never will be (eg. redis, memcache, elasticsearch, aws, grpc, the list is endless).<p>I appreciate the simplicity of just 'standard library only' to get started, <i>realistically</i>, is it meaningful to talk about?<p>I doubt you'll ever write a service that is 'standard library' only.