Replying to @⁨fistac0rpse@fedia.io⁩

Picture the level of quality and performance we could have if we had both traditional optimization AND upscaling optimization AND frame gen optimization.

Cause holy fuck the number of times I’ve seen fsr/dlss slaped onto a game and no effort put into making it perform well.

Cause there IS work you can do to make fsr/dlss actually look good and perform better.

Replying to @⁨ramble81@lemmy.zip⁩

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.

Replying to @⁨boonhet@sopuli.xyz⁩

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.