That wasn't the only issue with communism. It was so inefficient it failed to make enough food. Soviet style central planning was popular in India as well, which was a democracy. Resulting shortages and low economic growth led to what was avoidable deaths and malnutriton. Once you take price out of the picture, society stops being self-organizing and has to be told what to do. That socioeconomic system failed horribly and yet people keep trying to spin fantasies about it.
It isn't anti-technology, it's anti-capital/anti-big-business. If you don't allow businesses to scale-up because billionaires are bad, then you're biggest companies will be those that are from the previous century.
> Europe’s lack of industrial dynamism owes in large part to weaknesses along the “innovation lifecycle” that
prevent new sectors and challengers from emerging. These weaknesses begin with obstacles in the pipeline
from innovation to commercialisation. Public sector support for R&I is inefficient due to a lack of focus on disruptive
innovation and fragmented financing, limiting the EU’s potential to reach scale in high-risk breakthrough technologies. Once companies reach the growth stage, they encounter regulatory and jurisdictional hurdles that prevent
them from scaling-up into mature, profitable companies in Europe. As a result, many innovative companies end
up seeking out financing from US venture capitalists (VCs) and see expanding in the large US market as a more
rewarding option than tackling fragmented EU markets. Finally, the EU is falling behind in providing state-of-the-art
infrastructures necessary to enable the digitalisation of the economy.
Elm + Scala works for me. I'm using the same elm source with minor variations for both web & mobile (wrapped with cordova). So far, it's been working wonderfully.
The elm architecture removes the need to make decisions when it comes to structuring the app. The tooling is first class. While I'm not sure, I think elm has a larger community.
It's better to have it the other way around. Attempt to boot off the network and fall back to local drive. That will allow you to reimage a node without having to fiddle with the BIOS. For regular boot there should be no image configured. Network boot will fail and the node will boot off disk. However if an install image is configured for that node, you can reimage it at will. The install image should reset to having no image for that node, once it's done.
You'll need to maintain an association between - dns, ip, mac address, ssh keys etc.
Hardware break-fix workflow is usually ignored by most production engineers. You'll be doing that a lot. You want to get your hw back into use as fast as possible.
Have you thought about how many spares (CPU, RAM, disks) you'll have to keep at your datacenters ?
