• 2 Posts
  • 523 Comments
Joined 1 year ago
cake
Cake day: June 6th, 2023

help-circle









  • Some parts of London. I used to live in a building next to three sets of railways: the tube, regular intercity and express/higher speed intercity. That’s a bit too much railway outside the window. And that’s not even the worst location, in the New Cross area some residential buildings are sandwiched between railways on all four sides.

    Don’t get me wrong, I love trains in London, so many trains means I don’t need a car, but London has the oldest railway infrastructure in the world and the way they were built in the 19th century makes some areas a total disaster today.

    On the other hand, riding a DLR train through a skyscraper is bloody epic!




  • People don’t run just a single app in their machines

    That’s not bloat, that’s people running more apps than ever.

    the end result is the necessity for a constant and fast increase in hardware resources.

    That’s not true. 8 to 16GB RAM machines became common in early 2010-s and barely anyone is using 32 gigs today. Even if we look at the most recent Steam Hardware & Software Survey, we will see that even gamers are pretty much stuck with 16 gigs. 32 gigs are installed on less than 30% of machines and more than that is barely 4%. Ten years ago 8 gigs was the most common option with 12+ gigs (Steam didn’t have 16gig category in 2014) being the third option. The switch to 16 gigs being number one happened in December 2019, so we’re five years in with 16 gigs being the most common option and more RAM is not getting anywhere close to replacing it (47.08% for 16 gigs and 28.72% for 32 gigs as of May 2024).

    Now if you look at late 90-s and 2000-s you will see that RAM was doubling pretty much every 2-3 years. We can look at Steam data once again. Back in 2008 (that’s the earliest data available on archive.org) 2 gigs were the most common option. Next year 3 gigs option got very close and sat at 2nd place. In 2010 2GB, 3GB and 4GB were splitting hairs. 4GB option became the most common in 2011 with 3GB variant being very close 2nd place. 5GB option became the king in 2012. And the very next year 8 gigs became the norm.

    So, 2 gigs in 2008, 4 gigs in 2011 and 8 gigs in 2013. You can check historical data yourself here https://web.archive.org/web/20130915000000*/http://store.steampowered.com/hwsurvey/





  • All these packages don’t take much memory. Also tree shaking is a thing. For example, one of the projects I currently work on has over 5 gigs of dependencies, but once I compile it for production, the whole code based is mere 3 megs and that’s including inlined styles and icons. The code itself is pretty much non-existent.

    On the other hand I have 100KB of text translations just for the English language alone. Because there’s shit loads of text. And over 100MB of images, which are part of the build. And then there’s a remote storage with gigabytes of documents.

    Even if I double the code base by copy pasting it will be a drop in a bucket.




  • First of all, 350MB is a drop in a bucket. But what’s more important is performance, because it affects things like power consumption, carbon emissions, etc. I’d rather see Slack “eating” one gig of RAM and running smoothly on a single E core below boost clocks with pretty much zero CPU use. That’s the whole point of having fast memory - so you can cache and pre-render as much as possible and leave it rest statically in memory.