>> 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.
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.
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.
On iOS luckily enough I found Apple Maps to have crossed the good enough threshold for most of my purposes and area, except for the occasional live and timetable transit info.
>> you can never protect its (gold's) value, since this will be diluted if someone else brings a lot of gold to market... Bitcoin prevents this by automatically adjusting difficulty.
It doesn't prevent it. If everyone decides to sell BTC now (including the big whales owning the major portion), it's price in USD will fall, too. How is this different?
What I meant was that newly mined gold can cause extremely large flows into the market (much more than all the whales dumping at once), which is what happened ~300 years ago. Gold had large geographic differences in the difficulty of mining it, which Bitcoin solves through adjusting difficulty.
Everyone is praising GNOME here. Am I the only one who thinks that it's not polished enough? I'm using it on my laptop and it kind of works most of the time. But there are occasional bugs arising here and there. I even sometimes think that I'm the first user otherwise how come nobody noticed those (sometimes very obvious) bugs. If 26 isn't fixing them, apparently I'll have to move back to the Cinnamon spin.
I think GNOME 3 has come a long way but years later I'm still bothered by their killing type-ahead navigation in the file dialog and replacing it with search -- however useful searching may be (and despite recent improvements), it slows me down greatly, and often leads to mistakes, when I know where something is and simply want to navigate to it.
Plenty of discussion about this [0] [1] but the GNOME devs don't want it back, for various reasions.
Ubuntu has always patched it back in, but it looks like they will drop it in 17.10 if nobody steps up to maintain the patch [2].
Yes, i got some little things here and there, but in general it's a very good experience working in gnome these days and fedora took it to a whole new level of polish.
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.