by hexage1814 on 3/2/25, 2:27 AM with 147 comments
by sim7c00 on 3/5/25, 9:15 AM
I’m running 24 threads at 5GHz, sipping data through a GB pipe, and somehow, sites still crawl. Apps hesitate like they need divine intervention just to start. Five billion instructions just to boot up? My 5GB/s NVMe too sluggish for a few megabytes of binary? What the hell happened?
The internet isn’t just bloated—it’s an executioner. It’s strangling new hardware, and the old hardware? That’s been dead for years. Sure, you can run a current through a corpse and watch it twitch, but that doesn’t mean it’s alive.
by trinix912 on 3/5/25, 8:09 AM
by mahrain on 3/5/25, 8:29 AM
by dredmorbius on 3/5/25, 9:05 AM
For most local applications, or simple over-the-Web fetches via curl, wget, etc., mid-aughts hardware or earlier often suffices.
Amongst my hobbies are occasional large-scale scraping of websites. I'd done a significant amount of this circa 2018-19 on a mid-aughts iMac running Linux. One observation was that fetching content was considerably faster than processing it locally, not in a browser but using the html-xml-utils package on Debian. That is, DOM structures, even when simply parsed and extracted, provide a significant challenge to older hardware.
I had the option of expanding RAM, and of swapping in a solid-state drive, both of which I suspect would have helped markedly (swapping was a major factor in slowness), though how much I'm not sure.
I'll also note as I have for years that this behaviour serves advertisers and merchants as a market segmentation technique. That is, by making sites unusable on older kit, in a world where physical / real-estate based market segmentation isn't possible, is an effective way of selecting for those with discretionary income to buy modern devices. Whom we presume have greater discretionary income / higher conversion rates as well.
(Multiple network round-trip requirements is also a way to penalise those making access from distant locations, as those 100--300 ms delays add up with time, particularly for non-parallelisable fetches.)
I'm not arguing that all site devs have this in mind, but at the level which counts, specifically within major advertisers (Google, Facebook) and merchants (Amazon) this could well be an official policy which, by nature of their positions (ad brokers, browser developers, merchants, hardware suppliers) gets rippled throughout the industry. In the case of Apple, moving people to newer kit is their principle revenue model as well.
by axpvms on 3/5/25, 8:51 AM
by Rochus on 3/2/25, 5:27 PM
A solution could be to put another layer on top of the internet. This could be done by means of a "presentation proxy", similar to cloud gaming, e.g. based on VNC, where only a VNC client is run on the old computer, and the browser is running on the presentation proxy.
by zokier on 3/5/25, 9:43 AM
by eqvinox on 3/5/25, 8:09 AM
by rahen on 3/5/25, 8:44 AM
by ironblood on 3/5/25, 8:53 AM
by everdrive on 3/5/25, 3:11 PM
by xacky on 3/5/25, 9:10 AM
by Sweepi on 3/5/25, 8:51 AM
1. Using uBlock Origin and NoScript would help
2. Sorry, but the AMD A4-1200 (2 Cores running at 1.0 (!) GHz, 4W TDP, Single Channel DDR3-1066[1]) was already slow when it was new back in 2013, it was introduced by AMD as a low budget *Tablet* option
3. Regarding Video playback: As mention in the video, forcing Youtube to serve h264 should help, since the iGPU supports h264 decoding [2][3]
This also makes me wonder: What does Youtube serve on this old machines? On my old Vega 56 (UVD 7.0 h264/h265/JPEG decoding support), yt runs without issues, but on the displayed HD 8180 (UVD 4.2, h264 decoding support) it doesn't? My current system has a Nvidia 1050 and gets served AV1, which the 1050 also does not support in hardware.My first instinct for yt's "auto" implementation would be to the serve a video in 480p and a codec the users hardware decoders supports, and if the user switches to a higher resolution, to serve it in av1 in order to preserve bandwidth. Maybe Youtube does not have access to the users hardware decoding capabilities, or they want to preserve bandwidth even at low resolutions.
[1] https://www.techpowerup.com/cpu-specs/a4-1200.c1706
[2] https://www.x.org/wiki/RadeonFeature/#index8h2
[3] https://en.wikipedia.org/wiki/Unified_Video_Decoder#Format_support
by rembicilious on 3/5/25, 8:46 AM
So I visit thing-i-want.com and it doesn’t load because NoScript is currently disabling JS for that domain. No problem, I temporarily enable JS for thing-i-want.com
The page refreshes and suddenly NoScript is disabling JS for 10 more domains!
That seems excessive, maybe the page doesn’t need ALL of those scripts to function. I will enable that cloudfront domain and that one that has “static content” in the name.
Page refreshes.
Okay it mostly works now but also NoScript is showing disabled JavaScript from 5 more domains!
..Anyways Sometimes sites are running scripts from 15 or more domains and sometimes they are nested 4 domains deep. It’s absurd and OF COURSE it overwhelms older devices.
If you want to use a modern browser on an older device, use a browser with a script blocking plugin
by zkmon on 3/5/25, 7:15 PM
Also, companies don't want to invest in supporting multiple versions at any point in time, and can't afford reputation risk by not forcing upgrades.
My company let's the employees to request for and get a software installed, but can hardly allow them to use the features! The Risk & compliance department wouldn't like anyone to work or use any software properly. Any moving thing is a risk.
by bee_rider on 3/5/25, 4:27 PM
Hah, posted as a comment to a YouTube video.
I know you have to go where your audience is. But like, block ads, block most JavaScript, don’t go on YouTube, and the internet is much better.
This shoves you off into a smaller sub-sector of the internet. But if you are somebody who is nostalgic for the era when the internet didn’t suck so bad, it was quite a bit smaller back then too.
by psychoslave on 3/5/25, 10:09 AM
by shortrounddev2 on 3/5/25, 3:16 PM
by ForOldHack on 3/5/25, 8:39 AM
by agumonkey on 3/5/25, 1:16 PM
by everdrive on 3/5/25, 3:07 PM
by cowboylowrez on 3/5/25, 11:37 AM
by barotalomey on 3/5/25, 8:56 AM