How has document creation changed in two decades that justifies two orders of magnitude more RAM and CPU performance, 10x power draw, etc.?
If your house was built with 100x the resources and consumed that much more power, and it took longer to turn on the lights or cook a meal would it be justified because the building process was easier and you could add new light fixtures more easily? That would be lunacy, but for some reason we think it’s OK in software to avoid the craftsmanship the profession demands while treat users like fools who should just accept that computers are faster so their apps should be slower. It’s garbage reasoning. The ergonomics of developers should always come second to providing the best for customers.
I can run xlookup functions on a 1000 row excel spreadsheet on my cell phone.
> Chrome spawns a million processes so if a tab crashes it doesn't end your browsing session
This one is funny, because
1) before Chrome pages didn't seem to crash (js could, but not the whole "page")
2) Chrome still crashes completely loads of times
(also it's not really related; Chrome is a fast application written relatively effectively)
But I get your point, and you are not wrong. I just wouldn't discount "cheap development" to be the primary reason.
Often times what's being optimized for isn't even the speed of experience and maybe that's ok. Chrome spawns a million processes so if a tab crashes it doesn't end your browsing session, VS code being written in electron means writing plugins is a breeze and thus has built a thriving ecosystem in a record amount of time. If nothing else the world of software is a lot more flexible in 2020 than 1990 and maybe people prefer that to raw speed (given there's not a huge demand for native terminal based applications there's an argument to be made)