you are viewing a single comment's thread
view the rest of the comments
[–] 171 points 2 months ago (22 children)

One silver lining about the component restraints, hopefully it drives people to start creating efficient software again. Actually optimizing what you’re doing to save on RAM rather than a gig per tab in Chrome.

  • source
  • hideshow 22 child comments
  • [–] 71 points 2 months ago (4 children)

    "Claude, make this software more efficient."

  • source
  • parent
  • hideshow 4 child comments
  • [–] 59 points 2 months ago (3 children)

    Wish that was the case for a lot of new video games instead of relying on DLSS or FSR to cover up their poor optimisation

  • source
  • parent
  • hideshow 3 child comments
  • [+] 38 points 2 months ago (2 children)
  • [–] 2 points 2 months ago

    What makes you think nobody does traditional optimization anymore? UE5 is so hard to get to run well, you do need to do all kinds of shit to make a game run well. I suspect most of the games you've noticed not running very well, are UE5 games.

  • source
  • parent
  • [–] 30 points 2 months ago (7 children)

    I'm in a community making open source firmware for the Centauri Carbon 3d printer. The thing has 128MB of of RAM. The smarter people in the community worked some magic getting Klipper working on these things, and we're still fighting to shave off a couple more MB in average use to get things working smoother.

  • source
  • parent
  • hideshow 7 child comments
  • [–] 1 point 2 months ago (3 children)

    A Lemmy community? Mjnd sharing the addy?

  • source
  • parent
  • hideshow 3 child comments
  • [–] 2 points 2 months ago (2 children)
  • [–] 12 points 2 months ago (1 child)

    Doubtful. Google doesn't give a shit if you have 8 gigs or 64 gigs, they'll keep shoving more functionality into Chrome and force the W3 specs that nobody asked for. Some of the worst offending websites when it comes to performance also want you to use their mobile apps anyway (think reddit, facebook).

    Anyway, there's a saying that I heard as a backend dev at a company using Java and Spring: RAM is cheap, devs are expensive. RAM going up 5x hasn't REALLY changed that... Unless you're at Cloudflare's scale, where a small change amounts for 100 TB total across a bunch of servers on multiple continents, which would've been expensive even before the prices went up. But in their case, that's across a bunch of machines so it won't necessarily mean a big enough decrease in RAM usage per server to spec less RAM on future servers. Rather, they have a bit of extra RAM to play with.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 1 point 2 months ago

    Chrome treats itself as the OS and in some cases they are right do so, but there is an actual OS already running behind it that can’t give up things just because chrome thinks they can do it better. It would break other things.

    Chrome is inefficient because there’s no universal agreement on what it should actually be responsible for. So it just does everything.

  • source
  • parent