What balance? As explained in the article, the Markermeer was basically dead. This project has given the lake a chance to get some balance in the first place.

And some more precision: this is about the uppercase Eszett. The lowercase variant has existed for ages, and before 2017 was officially uppercased into SS or SZ.

It still is officially capitalized to SS under normal circumstances; capital ẞ is an allowed alternative: "Bei Schreibung mit Großbuchstaben schreibt man SS. Daneben ist auch die Verwendung des Großbuchstabens ẞ möglich." (Deutsche Rechtschreibung § 25 E 3)

SZ hasn't officially been an option at least since 1996.

Your remark about isolation is not entirely true: when you run multiple services in one VM, there are still a number of shared resources.

Most notably, all services will share the same heap, so one ill-behaved service can bring down all the other services. The only way to prevent this, is to run each service in a separate VM.

And at that point, you are once again comparing one Go runtime per service with one JVM per service.

CoreOS used to do this, but stopped doing it: https://github.com/coreos/coreos-cloudinit/issues/334 Basically, they don't want server provisioning to depend on Github being up.

No, in order to mess with your repo, an attacker would need your private key. Github only publishes public keys. For more information you can check out https://en.wikipedia.org/wiki/Public-key_cryptography

GitHub doesn't even have your private key.

Oh yea, duh. Thanks for clearing that up for me, I get the two mixed up a lot. (which is bad)

One real example is the Netherlands and the rise of Philips: http://books.google.nl/books?id=sfoujAT3b_YC&lpg=PA104&ots=B...