this post was submitted on 08 Apr 2025
18 points (100.0% liked)
Linux
7022 readers
219 users here now
A community for everything relating to the GNU/Linux operating system
Also check out:
Original icon base courtesy of [email protected] and The GIMP
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
That's good advice, but I beg to differ about the perspective on browsers.
There are a very few browsers that only render content. Most do much more: tabs, bookmark management, cookie management, password management, plugins/extensions/add-ons, history management, JavaScript, downloads management... they're full-on mini desktops, and they do much more than just render content. And all of this - while useful and desirable to many people - costs, in compute and especially in memory. Unless you're running an Electron app, odds are that your the browser is the single largest consumer of memory on your computer at the monogamy moment. If I run Firefox, it even tops Factorio with multi-planet factories.
Unfortunately, Acid2 compliance is very complex, and the content of many websites is inaccessible without JavaScript, so the idea of just something like Evince for HTML isn't pragmatic. However, having an engine that only renders CSS and XHTML could still be useful. Many sites are either JS-free, or the JavaScript only adds functionality that might be irrelevant to the content: commenting and feedback support, for example.
Gemini has failed, but a really pared down browser can still be valuable, and a fair portion of the web is still browsable without JavaScript. I think OP's question is entirely rational, and practical.
An example that illustrates my point is epub, which is just xhtml and assets in a zip: images, yes. JavaScript, no. I can imagine a wrapper that does the networking to fetch assets, bundles the allowable ones into epub, and then runs an epub renderer. It would be an order of magnitude smaller, and cleaner, than even one of the minimalist WebKit browsers like luakit, surf, or vimb.
I run the smallest browser I can, and only open Firefox when I hit a site I both a) want to see, and b) requires JavaScript to be at all functional. Most online shopping stores fall into this category, but banking's another. I don't begrudge the more demanding requirements of those sites, but I don't want the needless resource consumption of Firefox when the sites don't require it.
Arguing about which browser does not make much sense to me because ultimately to render HTML with CSS in the way that the designer expected is the whole reason you need CSS.
ePub is interesting, but the functionality supported in the HTML is limited, as is CSS support.
You make an interesting point about JavaScript, but in my experience, the use of it is increasing, not decreasing.
I never said that Firefox, Chrome or Safari was required, there are plenty of light(er) weight browsers around, there's even a Wikipedia page about it:
https://en.m.wikipedia.org/wiki/Comparison_of_lightweight_web_browsers
My point stands, use a browser.