For the main full-featured distros like Ubuntu, Manjaro, Fedora, etc you don't even have to use the console for most software. They all have "app stores" with tons of stuff in there from the big hitters like browsers, big office suites, email, etc on down to random little tools for random uses.

I've also been using Linux for nearly 30 years now and am very comfortable with it, but I wouldn't expect your average Windows switcher to want to have to mess with the console at all period for any use.

I see this a lot and I genuinely don't understand it. I'm not saying it's not happening to you or questioning your experience exactly, it's just not been mine for a long time. I use Linux almost exclusively across a bunch of different devices and laptops and things and I can count on one hand the number of times I've had to use a command line for anything. One was when the proprietary Nvidia driver on my main PC got so goofed up I had to do some manual work to clear it out and reinstall it. Another was when the fingerprint reader on one of my laptops got in a weird state trying to dual-boot Windows and Linux (since it stores some fingerprint details internally) and I needed to manually wipe it. The latter wouldn't have been a problem for someone not doing weird stuff with an old laptop, though the former could potentially be an issue with a gaming PC.

Of course, there is a valid argument that having to go into it at all for any reason, even once, is too many which I don't disagree with. But on a decently supported machine with a good distro/DE under normal usage I just don't see there being a lot of situations where someone should be regularly having to resort to a command line.

KDE has pretty much always aimed (intentional or not) to beWindowsish in its interface, integrations, shortcuts, basic menus, etc. It works very similarly with how it launches built-in helper applications, handles network and internet integration, general window handling and options, and such. There are also themes that do a passable job of making it mimic Macs if someone prefers that.

I was/am a long-time Windows user who has been using Linux on and off since the late 90s and pretty much 100% for a few years now and it's been helpful for muscle memory and such. The couple times I've actually been in a position to introduce long-time Windows users to Linux they've preferred KDE. I'd always go for a KDE distro (even if Kubuntu, which I use a lot myself, since it combines the wide support of Ubuntu with KDE, although Neon is pretty interesting too) when suggesting something to a noob. I do like Manjaro but I might still lean towards Kubuntu or Neon just because there's so much documentation for the *buntus out there vs. Arch-based stuff, but either would be a good choice.

My recollection is they had to put some fixes in for 486 support on real hardware a couple years ago because someone discovered it only actually worked on emulators (maybe just qemu) which wasn't quite matching real hardware.

https://lkml.org/lkml/2024/10/...

I have a high-end 486 motherboard with four 72-pin SIMM slots and PCI slots that accepts up to 192MB of RAM. For some reason it can't handle four 64MB SIMMs so it won't do 256MB, but it'll handle three fine. Or one 128MB and one 64MB one. But adding anything more makes it not boot and it seems to be a chipset limitation. At one point a couple years ago I had it maxxed out at that complete with an AMD 5x86 120mhz, PCI USB, video, and sound cards and Windows 98 and it did work but... other than for funsies there's no real point. I could have installed modern Linux on it but again, not something I really need to do or would miss not being able to do.

I think it would have probably managed Windows 2000 for fun, but again, not really. It's just a toy at this point and I don't see a use a case for it. I think there are some embedded cores based on the 486 instruction set like the Vortex86, but I believe the current ones have implemented enough (or maybe even the complete) Pentium instructions to run more modern stuff. And nobody probably needs to continue running the latest, current updates either given they're embedded systems.

That was six years ago and in many places the actual lockdown/remote learning was a year or less. It also goes way back before 2020. COVID may have impacted a small number of kids a specific age for a time but that was a long time ago now and kids have had plenty of time to adjust back to regular school.

It took awhile for things to catch up after the death of Flash, but there are still whole websites out there with bunches of little games that specifically advertise themselves as bypassing school blocking and being able to be used on school devices. I used to have a friend who was IT admin of a small school system and it was always a cat and mouse game trying to block all that. If they give kids access to the web at all in a way that isn't specifically allowlisted then they're going to find a way around stuff.

I semi-single-handedly caused half my high school AP Calc class to fail. We had TI-82s issued and I figured out getting Tetris, Solitaire, and a surprisingly capable Mario-esque game on mine and gave them to a couple friends. I didn't anticipate them figuring out how to transfer them to others because on a TI-82 it was a little trickier than later ones, but pretty soon most of the class had them. The teacher was a wonderful older woman who just didn't really understand technology at all and I have a distinct memory of one of the vice principals stopping by class just as part of wandering around and the teacher saying something like "They're always so diligently working on their calculators!"

It didn't take long for grades to tank and issues to crop up, and within a couple years of that the teachers learned to force students to wipe the calcs every couple days and keep an eye out for obvious off-label uses.

Old hard drives, which a lot of old timers like myself would remember, were indeed made with Iron Oxide. It wasn't quite rust but close enough to earn the moniker.

Granted they haven't been made with that in ages but the name hangs on.
https://en.wikipedia.org/wiki/...

I remember reading a review back in the day about either the public beta or one of the first releases wondering why it was a picture of a hard drive in the first place. They mentioned that the average user has no idea what a hard drive is or what it looks like, compared to classic Mac OS's icon that resembled an external hard drive which made some sense given the SCSI legacy of it, so wondered why they chose that when everything else was so skeuomorphic.

I'm even more surprised they still stick with "Macintosh HD" as the title even when they've pivoted away from "Macintosh" as a brand (and even "Mac" for awhile) and it hasn't been an HD in forever. That even predates Mac OS X.

This is missing that all the early consoles had major price drops during their lives, and most of the sales happened after those price drops. Relatively few people paid the full original retail prices for the NES, SNES, Genesis, etc. Games varied somewhat more but older games tended to be a little cheaper too.

Meanwhile the last couple generations of consoles have stayed close to their launch prices, had a "Lite" version released, or have even gone *up* in price for various reasons.

I'm not sure why you think it has to be charging to have thermal runaway. You can find plenty of videos of lithium/etc batteries having thermal runaway without being actively charging. All it takes is a charged battery and physical damage.

Whether this particular case was warranted or not I can't answer, but it does say it had shown signs of deformation from the seat moving around.

Office 95, 97, and Netscape both used to do it too, and I think even Office 4.3 or whatever the last version for Windows 3.1 had a quicklaunch toolbar that sped up launch using similar methods. I'm blanking on others but I remember some other big software having agents that sat in the systray to speed up launch. I usually kept all that disabled because they just sat there eating memory when unused and the improvement in launch speeds wasn't worth it.

Everything old is new again.

My recollection with the early days of ReactOS was it was intended as much to enable using Windows drivers and underlying frameworks back when Linux and other options had much more limited hardware support, especially on the leading edge, as it was just for running Windows applications. Especially for stuff like graphics and wifi and DirectX where there was relatively limited support and being able to use vendor drivers and such would have been a big deal.

These days that's much less of a problem and stuff like WINE seems like it'd largely be the superior. Linux supports most hardware out of the box or very quickly, and what can't run is more of a software issue than an underlying lack of support issue. ReactOS might slot in as a replacement for embedded or specialized industrial uses, or maybe as an option for ancient/low end computers for people who still need to run Microsoft stuff, but I feel like it's increasingly irrelevant as time marches on. Windows is a moving target and they're still trying to get it to run Windows 2000-level stuff.

By and large NT 3.5x outperformed NT 3.1 on identical hardware. They optimized 3.5x a bunch and many people consider 3.51 to be the first "good" version.

As for using leaked XP code, that'd be an absolute nightmare from a licensing and legal perspective. I would expect Microsoft is constantly going over any project that claims to implement Windows features with fine toothed combs to make sure nobody has used leaked code. They've already plonked a couple projects like the kind of hilariously named OpenNT based on the NT4 leaks, someone trying to release an XP-based OS from leaked source would be in trouble real quick.

Most developers with much sense would avoid ever even the appearance of looking at leaked code. It could jeopardize them on any future project they might work on that happens to tangentially be related to either Windows core development or work on competing products/projects. When ReactOS did their big code audit they had to be wary of developers who had looked at it or were submitting patches clearly based on it, intentionally or not.