> The Law of Leaky Abstractions is a lie; abstract airtightly
This one... Our entire computing world is a pie of terrible abstractions held together by duct-tape and billions of man-hours spent working fixing those leaks.
Keeping track is one thing. Actually _running_ the Lernaean Hydra of an application in production is a whole another story. The amount of "housekeeping" you have to do to keep the thing afloat is astounding: cascading failures, distributing tracing, logging and diagnostics, metrics. Even operational side of things require a lot of attention. Presumably, each microservice would require at least a minimal level of admin-level tooling around it.
Not to undermine author’s efforts, but I feel we as an industry took a wrong turn somewhere. An entire book on what essentially is a single Git command is just insane.
> There's nothing wrong with having zillions of them...
There's nothing wrong until something goes wrong an now you're royally screwed. With zillion dependencies you are at a mercy of zillion maintainers, and none of them has any obligation to you. They can break backwards compatibility in patch releases, introduce subtle behavior changes, steer the project in an unexpected direction or abandon it altogether.
...in consideration of the foregoing and the mutual covenants and agreements herein contained, and intending to be legally bound hereby, Parent, Merger Sub and the Company hereby agree as follows...
If by "designed" you mean "picking a content-addressable DAG as an underlying data structure", then yes, it is really beautiful. If you mean "provide a sane level of abstraction over said data structure", then hell no!
And nothing from Apple yet, right? Apparently, engineers are hard at work releasing a fix, so there should be known workarounds. Or at least it’s known to them what is actually causing the issue. Instead, we have hordes of people resetting their iPhones, adjusting dates and times, fiddling with notification settings and generally stumbling in the dark.
What would hurt them more, I wonder: publicly admitting that there is an issue (on a massive scale) and listing workarounds, or keeping total radio silence and then publishing a “whoopsies, we screwed up” after the fix is ready. All the while all their support centers are drowning in calls.
NewHash is a terrible name - on par with Xbox One [X] and iPad New. Googling stuff will be hard, and good luck explaining to less technical-savvy users what is this all about.
Plus, in 100 years, when SHA-256 is compromised, what would be the name of a new new format?