That's great idea. As long as you have that from the design , that's very cool. Moving existing infra to support the idea is just hard and quite a nightmare. In our new clusters, we apply that idea you've shared.
But...I don't care about the technology. I care about the object storage available to me without caring about the technology. So what's this do for me?
It's about time for the "adding new words" portion in the Google What-The-Fuck-Is-This-For product cycle. Last time we had that was Allo and Duo, before that was Plus. The "filler projects" just have normal nouns like Inbox or Photos or whatever.
And unless I'm mistaken, the people at Maker never said it was hard-pegged to the dollar. It was a soft peg, so the price could fluctuate here and there, but remain roughly stable.
> There will be no breaking changes from Beta 3 to stable, so our changelog should be short and sweet. Expect some linting, Sass variable improvements, updated docs Examples, and more build tool improvements.
Nice! We can finally use Bootstrap 4 without expecting future breaking changes.
The Ethereum "ice age" is a mechanism to ensure smooth transition to future planned hard forks. By tweaking the difficulty adjustment formula to artificially increase block times after some time (the so called "difficulty bomb") it makes mining on the old chain unprofitable, and incentivizes everyone to move to the/a new one. The general idea is to prevent extreme conservatism and stagnation w.r.t. hard forks, as we are seeing in Bitcoin.
Incidentally, in Bitcoin, large mining pools do not have control over the consensus rules. It doesn't matter what the miners say, their chain is worthless if people refuse to run it.
In Bitcoin, the economic majority decides what is Bitcoin. And when there's a substantial disagreement (e.g. BCC) there's a fork.
Large mining pools have no more power to enforce consensus rule changes on others than anybody else does.
The former offers far more visibility than the latter for say in the future.
So yes, IMO it is.
Otherwise private concentration of power will do as it always does: leverage it's monopoly to control the system as a whole.
The discussion & development are in the open. The large mining pools can sit at the table and discuss the changes as a part of the community. Or fork off.
I was the one who added Yarn to the official docker-node image[1][2]. This was the most popular docker-node feature request at the time. We managed to achieve it with a minimal size increase (with the help of the awesome Yarn team) and without affecting anything else. There was already a history of us providing some bonus features which the upstream Node project doesn't, such as a musl-libc build (for Alpine Linux).
