™

I had the opposite experience with Windows (7 up to 10), every now and then I would have to reinstall it to get some random feature working, which made the system run smoothly for a while - which checks out, considering Windows’ affinity for software rot.

Then again, I increasingly debloated it as time went on, which I’d assume contributes to its instability.

I’m not sure about specific packages, but in general a packager may not want to increase the upstream version even if they can do it themselves - for example, they may have made some mistake in the packaging process.

A recompilation or repackaging of Linux 6.6.6 is still Linux 6.6.6

Gotta recycle this:

That’s exactely what happened in my mind when I was getting started with Linux (kind of), although it’s arguably a habit that comes from using Windows where people don’t really think about OS users and permissions

I don’t think references are variables: you can’t modify them, and AFAIR you can’t have pointers to them, with the possible but unlikely exception of non-static member references.

I’m very confused by this thread.

Progress bars are handled by the applications themselves, whether flushing happens or not;

immediate flushing does not increase storage lifespan, in fact letting the OS decide when to do it may allow wear-leveling to work better.

(Though, IMO immediate flushing should be the default for removable media on user-friendly distributions, like swap partitions are)

Hot take: A scripting language is a programming language whose execution starts from the beginning of the file | stream.

They’re rubber-duck debugging

Jokes on them, the Covenant have broken long ago

do what they say

It’s not the case with this meme, but in C++ template definitions have to be defined in the headers if they’re not full template specializations

I would rather say that Christianity is open source, but it’s distributed with the MIT license and every relevant implementation is closed source and plants DRM software all over the system

Disabling swap does not prevent disk I/O from becoming a problem under memory contention, it simply shifts the disk I/O thrashing from anonymous pages to file pages

While the rest of that post matches my understanding of swap (I still think 1GB is next to useless in this case), that summarized point perplexes me.

What non-special file(s) does the kernel write to and read from, and how does it know how much space to use?

What fucking book?

w… windows 10?

I’ve been using Wayland for a while, and I’ve seen more bugs with my WMs than in my ~1000 hours of Deep Rock Galactic playtime

Perhaps Plasma automatically sets the various enviornment variables to enable consistent themes? I haven’t used it in a while…

There must be GTK somewhere, gtk3 is a dependency on Arch and the GTK_USE_PORTAL env var strongly suggests GTK has something to do with the file chooser. If they’re going to have to reimplement the latter, I hope it’s going to be less horrible than the GTK one but knowing Mozilla I’m not that faithful…