> 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.
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).
Why is it always assumed that the "company" was based in Bulgaria? Which "company" is it? As a Bulgarian myself I've seen that mentioned several times in the past, even on reputable sites, but never seen any actual evidence.
Well no, actually. Good Nvidia cards are also nearly extinct, because they are actually still profitable for Ethereum mining. So when people couldn't find AMD cards, they settled for bying Nvidia.
Unlike the situation with Bitcoin a few years ago, Nvidia cards are ok for mining Ethereum (something like 40-50% lower hash rate than AMD, but still very much profitable).
The truth is almost exactly the opposite of what you say actually. Yes, Arch is more difficult to install and configure the first time because it requires you to actually understand the steps it takes. But the top quality documentation really makes that not so difficult.
Arch is actually much _easier_ to maintain afterwards (once installed and configured) than almost anything else. This is because it does not add layers of useless abstraction, very much unlike DEB and RPM based distros. Packages are very close to upstream, with only minimal patches when really necessary, unlike RPM/DEB distros which heavily customize and patch most packages. Packages are also very easy to create, you can learn to do that in minutes, again very much unlike DEB and RPM which are needlessly overengineered and have whole ecosystems of helper scripts aiming to help with that complexity, but you have to spend a lot of time to actually learn them as well.