2698
Firefox is the only way.
(lemmy.world)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 13 Aug 2023
2698 points (100.0% liked)
Memes
45729 readers
595 users here now
Rules:
- Be civil and nice.
- Try not to excessively repost, as a rule of thumb, wait at least 2 months to do it if you have to.
founded 5 years ago
MODERATORS
You probably missed a part where Chrome, Chromium, and CEF are practically the same thing when it comes to resource consumption. Man, I can't even make Steam consume less than 1 gb ram at any time anymore, even when minimized. CPU consumption, the amount of processes, loading times are also problematic. I wish companies would rely on a labor of programmers, not just web programmers.
Bullshit. Steam works well when CEF isn't working right, like no internet connection. Images are still loaded. It's 100% thier storefront.
Reading comprehension level: 0
Sorry what? I literally said that it consumes this amount of memory while there is no active windows. You can close them all and it won't change much.
Also years ago the website was still filled with images and it didn't consume that much.
Also, do you really think high quality images consume more resources? High resolution I can understand, but quality is irrelevant when it comes to ram.
You seem to not understand what you are talking about.
First, it's possible to have an app active without spending resources on background windows. This process is called "close a window". If an app has the tray icon available it should be perfectly viable option and, guess what, it works like that with many apps. But no, even the tray menu for Steam is now a damn web-rendered element. Also even in Chromium based browsers, you can have 2 or more windows opened, and when you close one of them you can expect less ram usage than before you closed it. I've seen at least one VScodium derived app that completely unload browser based code when no active windows are visible. You don't need to be a huge corporation to know how to do it.
Second, it's insane to propose that thousands of images from some site (or even from disk cache) are going to be cached into memory immediately upon app launch. You could at least do some research or try Steam app yourself. Want to also tell me how I need thousands of images in my ram even when using Steam small mode?
Third, you mustn't tell me what I need to sacrifice to have "nice and smooth experience". I know enough about code and have seen enough apps to know that you don't need to require GBs of ram from every user to provide good experience. There are literally web based alternatives to CEF that consume 5x-10x less. And then there are many other options for native code.
You mention few megabytes of code. Yeah. Problem is, Chromium code is tons more than that. Those are not "small" apps.
Eh, after all, they are all chromium under the hood. So I'd expect similar cpu/ram usage from them.