[RandomKid]

>> defining sane defaults is the responsibility of frameworks and not a core library

But...but.. Golang core team teaches us that "framework" is a 4 letter word and a core library is enough for everybody. No need to overcomplicate with extra abstractions, just use the standard library they say.

[tyingq]

Not sure if that's a jab at my post. Not trying to be controversial. But, it doesn't appear that the example code shown for returning a json response even sets the Content-type header to application/json.

Since there's obviously some time lag before frameworks that use this core library will appear, good documentation on this sort of thing seems advisable.

[RandomKid]

That's not a jab at your post. Look at Swift and the way they encourage creation of new frameworks and server applications [1].

Then look at the hostile atmosphere in the Go community and tweets of its core team members stating that "http" package is great for everything, no need to use anything else. The framework (or as they prefer to call it toolkit) authors are throwing shit at each other accusing their opponents of creating something not "in the spirit of go" / unconventional, usefulness for the end users is not taken into account. Some others are creating posts about how everybody should stop creating frameworks immediately because that makes them uncomfortable. People hesitating to open-source their code because they are afraid to become a victim of crusade. That's not exactly healthy athmosphere, and it is nourished by core team members.

[1]: https://swift.org/blog/server-api-workgroup/