Recently posted comments

Why? The goal is to undermine all sorts of restrictions that are placed by the owning class on users. Patents are, in this regard, no different to copyright.

It pains me every time I see a Gitlab or ADO build with steps that takes 10 seconds (or longer!) to download a container image and start it to run a process that completes in 2 seconds.

By now everyone knows about "computational photography" and how it allows two smartphones with the same hardware sensors but with different signal processing teams to produce very different looking photographs.

Next, take a guess about laptop speakers. OK, not that big of a difference but you get the idea.

That sounds like it would just make hash collision attacks a lot easier (not finding the collision but using it once you found one).

A world where Linux ran on only 95% of the types of systems it does now, and the other 5% moved to Free/Net/OpenBSD or another kernel, but each group could focus on making their part the best would probably be a good world.

Sometimes there are tabs that just use up lots of resources (RAM, but mostly one full CPU) in the background, despite disabling service workers, so I still do that.

First detailing the memory issue I see: For me it's generally youtube, but I expect the same happens on other "infinite scroll" sites, particularly image (thumbnails for youtube) -heavy ones. My particular issue may be exacerbated by extensions, likely either HoverZoom+ when actively hovering over many thumbnails over time (thus assuming the memory for those is leaked), or, someone else's theory I read, that uBlockOrigin's blocked connections somehow don't fully close and thus leak memory over hours of blocking youtube ads, etc.

Regardless, using a single tab for hours on youtube, either searching (with perhaps a thousand hover-zoomed thumbnails over several hours), or playing multiple videos (tho fewer longer videos doesn't seem to leak as much as many short ones, could be from either many more blocked ads or many more thumbnails loaded, tho with fewer zoomed than the first scenario) eventually uses multiple gigabytes of RAM, even sending me gigs deep into swap on a 16 gig RAM system if I let it go long enough. (Tho I've never had it actually crash, likely because I have an equal 16-gig swap partition on each of four SSDs (so I can stripe them using equal swap-priority values for all four), so 64 gig swap in addition to 16 gig RAM, and I've never let it get beyond single-digits gig into swap.)

In the search scenario, if I middle-click to launch the actual videos in new tabs, then close those tabs in a relatively shorter time to go back and search further from the main search tab, the newer tabs don't seem to accumulate as much and closing them doesn't seem to release much either -- the big memory usage is all in the main search tab that has stayed open. And simply refreshing the page doesn't reclaim the lost memory, nor does deleting cache (which is on tmpfs so does use some memory), so the culprit isn't the tmpfs cache. And FWIW, forcing garbage collection from about:memory doesn't help either -- whatever's leaking, firefox doesn't consider it garbage to be collected!

*BUT*, either duplicating the tab (along with its session history) and closing the old one, or (with another tab open, say just open a new-tab to its default page, or one of the separate-tabbed video pages, so the entire browser doesn't close), closing the offending tab and immediately doing a reopen-closed-tab, keeps the tab's session history, but releases all that leaked memory, sometimes double-digit gigs of it!

So I don't close/kill the entire browser, I simply ensure at least one additional firefox tab is open so the browser itself doesn't close, then either duplicate the leaking tab and close the old one, or close and reopen the leaker. That gets my RAM back without killing the full browser.

Perhaps you'll find that useful as well, tho admittedly, in some cases it's likely less hassle to just do the kill and restart thing. (Much like after upgrading various in-use libraries and apps, while reverting to a text-mode login and running something to tell you what's still using deleted/stale files and restarting it, plus possibly having systemd reload itself too if it's on the list, can usually avoid a full reboot, it's often just easier to just do the reboot and get everything fresh all at once, rather than doing it one app at a time.)

> Good for you. But I hope you understand you are in a *tiny* minority.

Well, I did say this was for me, and that it didn't really apply to most Linux users (tho as edited -- believe it or not my original was much longer than that long thing above -- that disclaimer was rather weaker than my original).

Of course for many of us that's what makes Linux so great, that it's open and not forcing a single-size-fits-all solution on everyone. All those "tiny minorities" together may not make a majority (in Linux scope I guess that'd be Android), but together they're anyway a significant minority, and the larger Linux community would be missing something quite valuable without them.

I just recently had my new employer give me a decent wired headset.

The Ars Technica review ends with something like "It's cute _and_ functional, but for the price, you can get more performance", but, in my opinion, "cute and functional" is pretty much a USP. When I'm surrounded by my steamdeck, e-reader, tablet, yoga laptop, remarkable and boox, it's all black, black, black! Not cute at all.

I got this one for myself, all my other hardware is mostly for testing and developing Krita, and this is going to be for sketching a bit, doing write-ups and watching cooking videos, so I'm sure it'll be functional enough for that.

Plus, it's cute.

(I got the bubblegum version...)

Overall, I'm confused what the expected practice is here.

[1] https://lore.kernel.org/all/CAD=FV=UPjPpUyFTPjF-Ogzj_6LJL...

In comparison, Golang readily supports dumb caches because it stores the hashes of all the dependencies. If a cache tampers with a dependency, the download will fail.