I remember when my computer chugged trying to 95 after upgrading from 3.1!
And browsers now feel slow if they don't respond perfectly to touch input on my tablet. We used to tolerate much slower response times.
The second app took more than ten times longer, but it never left me doubting if it even noticed my click and how long I have to wait. That makes a world of difference.
90s era software was written in the expectation that the computer is slow, and having progress indicators on screen or in the status bar for a lot of tasks was common (and if that was too much work at least the cursor was updated instantly to show that work is done). Today most software is written in the expectation that everything works instantly, and if it doesn't the user experience falls apart quickly.
While now the UI is more regularly decoupled from the application, the awareness that updating the user seems to have somewhat fallen by the wayside, and so a big ol' spinner, or a largely fictitious progress bar that isn't actually tethered to any measure of work, shows up and you get situations like "well, the progress bar is at 130%, but I sure don't feel like I'm at 130%...".
This isn't the tools, it's a poor use of them, and it lends a lot of ammunition to folks who want to back-in-my-day while ignoring that a lot of other parts of the stuff we had back in our day kinda...sucked. Some of it (not everything!) just happened to be good at this one thing!
Indeed, even something like MS-DOS/Windows 3.1 or Amiga 500 would already be good enough for many office tasks that most people do.
I realize aspect ratio could be a problem and I'm willing to put up with some black on either side.
What is also awesome is that after it boots DOS on that page that the CPU utilisation by my browser is pretty much zero.
Presumably the processor is waiting for an interrupt, so there’s nothing for the emulator to do, so nothing for the browser to do.
I also found this (somewhat amusing) page discussing the problem:
The "Running the CPU at 100 percent for too long can damage your computer." message is probably legal ass-covering, since any system that can't 100% CPU usage 24/7 is defective. Indeed, back when DOS was common, that's what it did to the CPUs of the time, as did other applications which used a polling loop instead of waiting for interrupts.
Try running DOS in any VM and you'll be shocked by the CPU usage. A constant 100% until you install a little program called DOSIDLE that properly runs a HLT instruction when the CPU is waiting.
But apparently not for Electron apps...