"basically NT 3.1" is an incredible over exaggeration. Total RAM capacity has stagnated over the years and subsequent generations of DDR have backed speed instead.
8GB in a computer was considered good in a consumer performance machine in 2010. 16 years before that was 6-8MB.
I have a port of BuildGDX in the project backlog that was basically just throwing Claude at it to go from Java to .NET. The only thing it really got hung up on was Java's byte being signed.
What I ended up with was a port of Duke 3D that uses half the allocated RAM as DukeGDX.
We regularly play Dark Messiah at our LAN, and I got that working straight off the disc. The only issue I've had with Source is SDK 2007 mods, but only because it's _extremely_ hard coded to have the SDK in a specific location.
But yeah, games that do outright crash are pretty easily patchable and most likely already have been.
I'd like to know which ones you've had issues with. I've compiled a collection of hundreds of Windows games from ~96-2006 and I've only run into one that's required an appcompat flag (carmageddon 2).
It's also worth noting that semantic markup is not a feature of CSS, it is a feature of HTML. CSS has almost no power if something like a scraper or a reader mode chooses to ignore it. Of course that would be pandemonium and we would never get good results.
I feel like something in the CSS camp that could be highlighted in a "great idea, okay implementation, poor reception" that the OP is going for is print stylesheets. Those are incredibly underused.
To call a CSS pixel not an actual pixel but a measurement of an angle at a reading distance is... technically correct... but isn't really representative of how it's actually rendered. On a non Hi-DPI display at 100% scaling in the browser and OS, a px is a device pixel. An css inch is considered 96px, with the assumption that a CSS inch is an imperial inch on a 96 DPI display.
Yes, it's a bit fuzzy now with modern displays (especially when display scaling is not at a whole number haha) but it just kinda feels like searching for something to complain about. If your browser and OS doesn't get in the way you can get exact measurement. This also applies to almost any UI framework that has some integration with the OS.
They were only suffering and had great battery life because they were kneecapping their own machines with improper cooling. It's pretty obvious their last few Intel laptops were intentionally designed so that the M1 would look better in almost every way. It was still an incredible chip, but I personally didn't believe that it was a fair comparison.
We have similar issues here in Wisconsin. Especially when it comes to solar and battery storage facilities. I absolutely think there needs to be more regulations carved out for data centers, just as there is for any other industrial building, but yeah the great mongering is incredible to see. Especially when the argument of "save our beautiful farmlands" is brought up. Do you even know how nasty agricultural runoff is?
The argument is only fair if they provide some valid information to back up their claims. There's a project to put in a BESS near my rural hometown and every anti argument is based on non-LiFEpo cells and self-inflicted confused overlap with the data center water use arguments. This is while completely supporting "beautiful farmlands" that leech pesticides and phosphates into the water table
Comparing GitHub and SourceForge as if they were cut from the same cloth is laughable to me. SF has always been a wretched hive of ads and dark patterns.
Not that I disagree with you, but some of us still use desktops because laptops don't always get the job done. That being said, how hard is it to hit ctrl-s
8GB in a computer was considered good in a consumer performance machine in 2010. 16 years before that was 6-8MB.