How about they start by figuring out the concept of power efficiency in the web code that everyone runs? We could do a huge amount if we'd give every mainline

How about they start by figuring out the concept of power efficiency in the web code that everyone runs? We could do a huge amount if we'd give every mainline tech company engineer a Raspberry Pi 4, and shut down their big workstations for a week a month, making them live on a mere quad core 1.5GHz chip with 8GB of RAM. I'm sick and tired of how every shiny new "update" of web applications uses more and more CPU, runs slower and slower, and, gosh, you'd better buy a new computer to run it. I've ranted before on my blog about the horrible things Google did to the Blogger interface - a text editing interface. For reasons I don't care enough to dig into, the "new" interface forced on everyone last year has some dependency on number of photos such that if you have too many photos, or too slow a system, you get massive, massive lag in entering text. It's literally unusable on plenty of systems that used to run the older interfaces, and you can choke out a fairly high end system by putting enough photos (100-200?) in a post. Even a dozen or so will choke out older systems that used to run the old interface fine. But, hey, it's no problem for the Googlers who wrote it and tested it on their high end 2 year old Xeon workstations! Worked great for their toy cases, and having not actually talked to anyone who uses Blogger, ship it and get your promotion, having ruined the interface for anyone with older or lower power hardware. The new Google Chat interface I've been migrated to is similarly painful on a Pi4. It only takes 20 seconds to load and then maybe a similar amount of time to load an actual conversation. Snappy on a M1 Mini, though, so who cares, right? Once it's actually loaded, it's tolerable (the usual slight lag in text entry that any Google app on a Pi4 has), but getting it loaded is quite painful, and Hangouts used to work just fine.