At least in my experience, that ideal has never existed. "Engineering" (and "re-engineering" and "re-re-engineering" in the agile worlds) was always what I was spending the majority of my time on. Coding was a medium for the engineering. By the time I finished the engineering the code was either already finished, being discovered in the written code and then documented, or the code was "the fun part" reward for all the hard engineering work that lead to it (and all the ugly specs documents it took to get there).

I am certainly familiar with these things. I just don't see them having a practical effect on the average consumer, just fellow HN commenting nerds. I think I have one friend in real life with GrapheneOS at the moment, and it is not an experience they would recommend to any other friend of mine.

I support such things in theory, sure, but in practice, especially in HN comments there seems to be a lot of forgiveness to the very locked in by Google Android ecosystem purely because these alternatives exist, ignoring the practical realities such as marketshare/mindshare/ease of use/ease of access.

I don't have any easy answers on how to fix AOSP because it seems to be a sociopolitical problem, not a technical one, and I am mostly just complaining without skin in that particular game because I can't find myself caring about Android politics, but when my less technical friends and family that prefer Android are upset at something Google does I don't have good answers because "do months of research into LineageOS or GrapheneOS, deal with most of your apps not working most of the time, and it getting harder to buy phones because you have to make sure that they are rootable" isn't a good answer. "Why don't you just switch to an Apple device?" is at least an easier answer.

    Location: /search/?queryHash=SOMECDNHASH

Sure, it is more work for your webserver to compute that and potentially the browser to cache it's knowledge of that QUERY, but it potentially gives you an advantage in keeping things like CDN edge caches generally aware of client/browser caches in a way that can be performance optimized.

[1] https://www.rfc-editor.org/info/rfc10008/#section-2.4

What is AOSP really for other than "open source washing" Google's ecosystem? Is it ever making standards that Google has to follow/comply with or is it always just the tail being wagged by the dog to make it look like the dog is happy about open source (but still isn't majority open source)?

Low quality "spam" tactics still reel in enough fish to be monetarily worth the "backlash" from customers that find it distasteful and or start to lose trust in the company. The "We promise we don't spam people" metrics and "Consumer distrust" metrics don't talk enough to the "revenue" metrics, but especially have very different cycles: big customer satisfaction metrics like J. D. Power are big annual things, not quarterly reports like earnings. In my experience things like "how often are we calling the same disinterested people to the point where it starts to feel like very personal spam" metrics don't ever really get prioritized in internal reports unless there's enforcement from Legal departments, and even then Legal departments can't "upset the bottom line" and only care about such compliance when it becomes News and/or Lawsuits, both of which don't even merit even an annual review cycle. (In fact, the modern class action lawsuit pretty effectively prevents that feedback mechanism from cycling, because generally the terms of agreement in a settled class action lawsuit is that the class is no longer allowed to sue again for the same problem, even if the same problem keeps happening and is never actually fixed.)

Unless quarterly earnings reports need to include things like client satisfaction and spam tracking, the only metric management will continue to care about, because it also is the only metric shareholders claim to ever care about, is the "bottom line", no matter how ugly the sausage is made to bump it from quarter to quarter.

Git does very well at the 80% and with tools like custom merge tools and git lfs/annex and git sparse "cone" checkouts can get pretty close to hitting the 90 or 95% case.

But yeah, so many of those extra tools in that 80 to 90% area are awful to work with because they aren't the default, aren't out the box, are hard to configure and get right. Partly because it always seems like there will be a gap in that 95%-100% window and partly because the use cases that need that 80% to 90% often are only "just 10% of use cases".

(Which is also to say that to survive Jujitsu and Pijul and others seem to have to work to make sure they handle the 80% base case extremely well just to compete with git, they haven't necessarily time to think about the 90% or 100% problem.)

(ETA: And also relates to why game development seems to feel the 20% cases more, because by volume of data game development is certainly closer to a flip of the 80/20 sides with 80% or more large binaries by volume.)

PCs were designed to be general hardware and it didn't seem to make sense to create a generic "PPU" for the PC, so instead game engines at the time (and many game engines to this day) had to emulate one entirely in software. The video RAM of EGA and VGA is just one big blob of pixels, or perhaps two if your system supported double-buffering. At the hardware level it doesn't have concepts like sprites or scrolling backgrounds.

Carmack was one of the first (if not the first; Commander Keen was also among the first commercially successful attempts) to get a software "PPU" renderer on the PC working reliably in real time. Another notable achievement for side scrollers on the PC in that era was Cliff Bleszinski managing to software render the parallax effects similar to Sega's "Blast processor" PPU (notable for "gotta go fast" Sonic games) for Jazz Jackrabbit (in 1994).

It has sort of long been the arc of PC development of eventually doing entirely in software what consoles and arcades were doing with dedicated and/or one-off hardware. (Right up until about the invention of the modern GPU when suddenly the PC was leading graphics hardware in a different way.)

[1] https://www.nesdev.org/wiki/PPU

At this point it does seem easier to not have to look up if something is NewsCorp Fox or the parts of Fox that Disney bought because Disney no longer calls them Fox.

A US city often overlooked for some intricate people explorable underground spaces is Cincinnati: https://www.visitcincy.com/blog/post/unmistakably-cincinnati...

Some of Cincinnati's underground exists from plans to build subway trains that never completed. I think that makes Cincinnati's particularly sad being that it constitutes a perpetually unfinished public works/public transportation project.

Relatedly to that, Atlanta also has a tiny underground leftover from passenger train lines that ended passenger travel decades ago (and so was turned into a mall, because America): https://en.wikipedia.org/wiki/Underground_Atlanta

(Others point out that Calibre automatically will rename epub files to .kepub.epub for you if you use it to manage a Kobo library. It's just manually copying files to Kobo where you need to remember to do it yourself if you have a Kobo.)