a bit of the problem is that modern elements like display + touch screen require a lot more bandwidth than 3110 - for example the displays require ridiculous bandwidth in comparison to the nokia, like 10 gigabit/s for Samsung Galaxy S25 (basic model, not plus/ultra), plus connectors for the cameras.
At the very least you can't really make the screen soldered-on, and the simple connectors used in Nokia might not work out for such high bandwidth use case. Same with cameras.
Thin ribbon connectors are one of the hardest things to automate from what I remember regarding Sony's efforts to automate PS5 manufacture.
Also the set of supported/accelerated operations in the fastest path is different no matter whether you use 8, 16, or 32bit floats, thus the common use of "TOPS" as benchmark number recently.
TSA including all of its security theatre was on life support because of insurance premiums - it allowed some creative actuarial accounting that shifted responsibilities and reduced insurance costs for airlines in post-9/11 insanity
Yeah, recent news are essentially raising this from "crossing US border is dangerous, prepare yourself" to "US border guards got a quota of terror to inflict, do you really want to gamble?"
Remember that there aren't as many drivers in VMS core as in Linux (were just amd DRM driver dwarfs some older kernel versions), and ACPI for all its complexity also handles as portability layer between a lot of differences that in VMS' past involved having to release an entire special release of the system just to get it to boot, now covered by ACPI support.
Also, we don't know how much of that is test code, samples (for testing, for example)
And what difference to end user it makes where exactly the key/value data is stored? No real difference whether the data is HKEY_CURRENT_USER\Software\MyAppName or com.my.app when you're trying to coerce some internals whose configuration is not exposed because you're not worthy of it
It was common in the Windows 9x days for the two Registry Hives (SYSTEM.DAT and USER.DAT) to get corrupted leading to an unbootable system or to get fragmented and/or full of disused values from poorly-uninstalled software leading to increased memory usage.
Here are some KB articles to check out for context:
I’d say that a quick defaults command is probably on the whole more friendly than trawling around in the arcane mess that is the Windows registry. It’s not as friendly as it could be, but at least it’s a somewhat human readable one liner.
It’s also reasonable to back up plists and/or sync them between machines like some users do with their dotfiles, because they’re just files.
There is - removing a wonk preference namespace is as easy as `rm ~/Library/Preferences/com.cheapskatesoftware.wonko.plist`. Whereas the Windows Registry is a monolithic piece of gunk you need a Microsoft editor for to zap something
I don't have the specific setup archived, but I believe my basis for it was a script included in winetricks at the time which installed Office 2013 professional based on offline 2013 proplus 32bit iso.
WineHQ reports that installer for 2013 64bit is "gold", but apps required few tweaks to be applied and Access sometimes failed.
Generally seems 2013-2016 era works on wine per few applications I checked
At the very least you can't really make the screen soldered-on, and the simple connectors used in Nokia might not work out for such high bandwidth use case. Same with cameras.
Thin ribbon connectors are one of the hardest things to automate from what I remember regarding Sony's efforts to automate PS5 manufacture.