Blame html5/css3/javascript which opened the floodgates to browsers needing to be resource hungry to do a huge amount of work to render pages sensibly without visible page rewrites flickering the screen for a number of seconds.
Outside of browsing there are also other resource hungry processes like video processing, CAD etc where you want the screen to run smoothly and quickly.
Then there are games![:roll:]( "Rolling Eyes")
which achieve speed by brute force rather than clever programming thanks to the use/abuse of game engines.
Run-of-the-mill apps can take very little resources, my 6502 and Z80 computers did wonderfully and still would if I blew the cobwebs off them over 40 years on, I think the SRAM/DRAM chips used more power than the processors even when double-clocked in the case of the 6502.
Outside of browsing there are also other resource hungry processes like video processing, CAD etc where you want the screen to run smoothly and quickly.
Then there are games
which achieve speed by brute force rather than clever programming thanks to the use/abuse of game engines.Run-of-the-mill apps can take very little resources, my 6502 and Z80 computers did wonderfully and still would if I blew the cobwebs off them over 40 years on, I think the SRAM/DRAM chips used more power than the processors even when double-clocked in the case of the 6502.
Statistics: Posted by pidd — Sat Aug 02, 2025 11:05 pm