I can make mistakes. It's on you to fact-check my claims.

Do you think these are harmless statements? Does the disclaimer suffice? If I was Google's AI Overview, do you think 100% of people will check those sources?

There is nuance here, and it's not going away because AI and innovation.

And it looks to me like we are mapping each row with a constant y, calculating the "distance" (thus scale factor) only once using just the vertical slope for the row.

This particular issue is solved in GitHub proper, and derives from the Windows 95 tree view widget [1], which I seem to remember from Windows 3.x but can't find a screenshot.

The hover behavior is just not an intuitive or accessible default. I can't imagine someone being able to use this if they have a hard time clicking without moving the mouse. It also wastes resources fetching file/directory contents while the user is moving the cursor to a predetermined file they presumably wish to open.

[1]: https://learn.microsoft.com/en-us/windows/win32/winauto/syst...

Just focusing on the demand-side dramatically reduced incidences of catalytic converter theft in the US. You still get the occasional attempt, but basically no scrap yard will take catalytic converters without a title to the vehicle with matching VIN, and most will want to see the vehicle.

Yes, requiring paperwork to scrap wiring is bureaucracy manifest. But legitimate people just do not roll up to scrap yards with a van full of tangled 4/0.

The big catalytic converter buyer was so brazen, he had a mobile app. Free markets for stolen scrap is just beyond tolerable at this point.

x86 still runs in real mode on boot despite dropping the PC BIOS.

Lots of software still assumes a 4kb page size, to the point where migrating Android to 16kb is an ongoing multi-year effort involving far too many people. And this is an OS for phones, which you might assume would lack the memory to benefit from a larger page size.

And one of the most popular consumer CPUs for enthusiasts, the Ryzen X3D chips, broke assumptions in both Linux and Windows schedulers that all cores have access to the same amount of L3 cache.

I would probably not assume the kinds of hardware limitations that we have now will persist into the useful lifetime of current software. Splitting the OS into "consumer" and "enterprise" variants is one of those moves that would bake in a ton of assumptions and make things messier in the future.

Is there a term for "reverse Roko's Basilisk"? That you are convinced society will trade your freedom and opportunity in pursuit of an AI superintelligence, so you learn bow-hunting and how to dress a deer carcass while prepping your Quonset hut in northern Idaho?