As someone who came to Go without prior work experience in web technology, I struggle to understand the value-added from building a tiny container that is barely larger than a single binary, instead on just working with that binary. I'm sure there's a reason for it, but I've yet to learn what it is.
Why was this submitted twice?
There's an extra %20 tacked on the end of the link address.
I'd be curious if people familiar with this technology stack would consider it "production ready."
Yeah, but can I then run the resulting Go code in the browser using GopherJS?
As someone who came to Go without prior work experience in web technology, I struggle to understand the value-added from building a tiny container that is barely larger than a single binary, instead on just working with that binary. I'm sure there's a reason for it, but I've yet to learn what it is.
Even though it's still early in development, I'm impressed by the documentation. Plenty of mature projects don't even have that.
I suppose the focus on Linux is to be expected, but I would still have loved to see something like this support Windows.
That's where I have the most trouble dealing with C code in my projects.