you can also flip these keyboard shortcuts around, which I did for the cmd-shift-4, as I almost always want it to the clipboard without persisting as a file
Berlin is also super unevenly populated and includes several forests. If you compare the density of the actually populated areas, like Mitte, you are still under Manhattan, sure, but only by a factor of 4 - which is extra impressive given the near complete lack of tall buildings in Berlin. Neukölln (which borders the area in question) is even more dense - about half as much as Manhattan [1].
Its unfair to compare Manhattan which apart from Central Park is nearly 100% urban to Berlin, which is significantly larger and includes many areas with widely distanced houses and forests.
I'm the OP of the DBA StackExchange post, and while yes, it does technically work in this case, you do lose some abilities. For one, its much harder to `count(*)` rows with `DISTINCT`. Also, `DISTINCT` uses a totally different mode in planning that requires first retrieving all the rows and then finally filtering them. This is _much_ slower and generally not very fun to deal with!
L4 and L5 are stable (see Jupiter's asteroid collection), but the others involve essentially trying to balance on a infinitesimal pinpoint, with any perturbation causing one to "fall off" and move away.
Sure, but automating this requires a lot more tooling. In the case described with multiple, widely spread instances, you'll need to be able to
a) Reliably determine which step you are on - this includes both migration steps and application deployments
b) Fully automate your deployments from a list of staged code changes ("normal" CD will have issue with this)
c) Fully automate migrations _after_ all deployments are complete
Those are all totally possible steps, but they are all going to vary based on your setup, making a drop in solution for this process unlikely to be easy.
Additionally, these are only the steps if everything works! What happens if there's a bug halfway through? You probably want to stop the deployment process and either revert or quickly hotfix. A human-based system can handle this quite easily, but an automated system will need to be able to measure errors and reliably determine if an issue exists.
So its not that this can't be automated, in fact, I know that it has for several large organizations, but the hurdle to get to the full level of automation is rather high and fraught with secondary issues to consider.
Not defending/attacking the phrase "disastrously bad", but I'm not sure its a fair argument to say "the docs explain it", if the behavior isn't what a "reasonable" person would expect. Writing software that deletes your files (when you expect, say, the weather report) isn't excused if they write in the docs "oh this weather software randomly deletes files for no reason".
In this specific case though, even those docs do not explain what happens if the value is "invalid"!