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.
>> 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.
>> 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?
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.
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/