I'd have to ask, what would a 16 year old know about the "humiliation ritual" of job hunting? They have near-zero non-school responsibilities, near-zero if not zero creditors, no mortgage, no CC, if a car payment/car insurance exists, parents are on the hook, etc. Getting a McJob is great for the experience, but unimportant in the grand scheme of what is actually required of them or the pressures of 'real life', not to diminish the importance of schooling.
And do we really care what a developer is, be it age, previous non-tech job experience, or any other metric? It almost seems like an Internet meme at this point.
Seems like the first part of that law would be struck down on First Amendment challenges.
Second would be technically impossible, or the responsibility of VPN providers to somehow forward geo-location information for website operators to consume.
I think you strung together a bunch of words that don't jive with real world experiences.
Windows 7 still had some fundamental kernel quality issues. WDDM 1.1 wasn't mature to the point of providing a stable experience across the board and vendors were still adapting to the WDDM model; kernel mode printer drivers were still common, both a stability and security knock for those older versions of Windows.
So no, Windows 7 did not have "all of the stability" of Windows 10 or 11.
Along with this, which is how nearly every major piece of software works today, removing telemetry likely wouldn't have a measurable impact on performance or memory usage. Those aren't heavy subsystems.
Windows 2000 had sequential service startup. It took /ages/ to boot. The boot screen was pretty, though.
XP was a security nightmare and out the gate was BSOD city, much of that thanks to 3rd party drivers, but the OS had fundamental kernel bugs, too.
7 was okay, but it isn't something you'd want to go back to with modern hardware. It lacks many features we find essential. TRIM being a big one. I'd argue that the Windows 7 iconography wasn't very nice.
I'm more of a fan of NT4 for it's utilitarian look, though service management was no where near as nice as what the MMC brought.
From a stability perspective, it really wasn't until Windows 8/10 where we got to the "PEAK" Windows versions, where stability was not an issue at the OS level with Microsoft-shipped code, but rather at a driver or hardware level. No longer were we seeing some fundamental kernel bug halting the system, instead it shifted over to garbage 3rd party drivers (largely fixed thanks to Windows' unique ability to restart the graphical subsystem/removal of kernel mode print drivers) or failing hardware. You won't find that level of stability in Windows 2000, Windows XP, or Windows 7.
Those production numbers for the Neo are global and from unnamed supply chain sources. I'm not sure why you brought the US workforce population into the equation as that mixes up scales, nor is there a 1:1 relationship between people and computers (I have 5 x86 systems and 2 M-series laptops in my home between work and personal use).
Lenovo shipped roughly 16m units in Q1 2026 at #1, with Apple shipping roughly 6m in the same timeframe at #4, WW. [0]
Linux is hardly a blip and even the Steam survey #s back that up if you want to be targeted towards a particular audience. It's a lot of noise in forums like this, not so much on the general street. Windows overall gaining ~1.1% with Linux overall declining ~0.8% (and macOS continuing to be poorly represented for obvious reasons) in April.
I'm happy for your personal experience; it clearly doesn't jive with the numerous threads on the macos reddit forum for first and third party apps causing OOM issues (which macOS ungracefully handles, unlike NT).
> Not sure what your intentions are.
This is just a weird statement.
> Yes, modern OS's might have issues in runtime
/All/ modern general purpose OSes have issues at runtime. Every last one of them. macOS isn't without it's significant UX and other faults. It's OK to acknowledge them; this isn't a religion.
It's not really that interesting in the landscapes of OSes; modern (or even ancient) Windows and Linux distros have been doing these tasks simultaneously in one form or fashion since 16GiB was seen as a lot of RAM.
See my other post for just a tiny amount of references to OOTB faulty apps.
It's quite clearly a bug and likely not one easy to diagnose or reproduce given the length of time the bug has remained in macOS. Or a fix would be a drastic breaking change.
Or Apple doesn't really care, though I doubt that's the case.
> it definitely matters as to how old they are, and how much they've done.
No, it doesn't. Either the tool is good/useful or it isn't. Everything about this tool is AI slop, from the website to the utility itself.