Not hard to find single cup brewers for loose grounds (I own one) and they’re cheaper because they don’t have to work with Keurig for licensing and compatibility.

Those aren’t bad but the container is too small for my liking. Keurig brewers are a pain to clean too.

Used coffee grounds have many more uses than the plastic k-cups. Recycling the cups is difficult and usually doesn’t happen. They do make eco-friendly cups but they still contain dyes for the labels and require more energy to mass produce than simple paper filters and a bag of grounds (or beans if you grind your own).

K-Cups. They might save you a grand total of a minute over loose grounds and a disposable paper filter, but they’re more costly per cup and create more waste.

I’ll buy them as “gag gifts” but not for myself.

Rage. The changes to 3rd party apps really pissed me off and I thought it was best to use my anger productively.

Don’t obsess about high school drama or let it get you down. Social interactions post-HS are completely different.

I would say listen but make your own choices and make mistakes (small ones). Parents are conditioned to protect their kids but that’s a poor way for you to learn real life lessons.

IDK about the RPi5 but earlier models don’t do well with transcoding. You’ll want to make sure to convert all of your videos to a format widely compatible with your clients. H264 is usually compatible with any device of the last 10ish years.

Only learning curve is naming. Jellyfin seems less forgiving about filenames and folder structure than Plex was.

How do you ensure your teammates don’t start committing their own IDE settings or committing “secrets.json” files or helper scripts or log files?

Disagree on the .gitignore file. If you’re the only developer and you only work off of one machine then it doesn’t need to be committed. In a team setting it’s absolutely imperative to commit it.

I’m definitely considering a dumb phone with tethering capabilities to use a less locked-down device.

Vanilla Debian on my old netbook does alright. I think my desktop is xfce.

Only thing better I’ve used is antiX. I moved away from that one though since they insist on not using systemd and it got to be too much of a hassle to work around (lots of packages assume systemd is your init). I think Void Linux is supposed to be similar.

Same. I started going to Flathub in my browser.

Embrace, extend, extinguish.

I would be incredibly weary if someone like Meta, Google, or Microsoft started their own distro. Make a solid distro with lots of bells and whistles few distros have, pre-install it on the hottest gear, poach the best devs away from open-source projects, exert more and more influence over kernel development, wait for a majority to get locked in and then start making parts of the OS proprietary so open-source can’t keep up, and the dominoes fall from there.

Me: Junior! Did you hack a Gibson???

5yo: Maaayyybe…

In theory, yes, but it wouldn’t be as significant as stopping it entirely (or pausing it instead of a hard start-stop). I only mention CPU limits because it’s extremely easy to implement.

If you use Docker/Podman to run Syncthing (a little tricky but possible) you can limit its CPU usage, which is usually the main source of power drain (besides GPU processes). If your usage is like mine Syncthing is idle 95% of the time and I wouldn’t notice if that 5% took longer than usual to do its thing.

Seriously? Number 1-4 are just outright stupid claims, or misguided explanations at best. I especially laughed at the “system being in read-only mode” stupidity. WTF do you think EVERY SINGLE Unix-like system has configured, world writable everything?

The important parts of the filesystem are mounted read-only so you’d have to explicitly reboot and mount as read-write. That’s a lot different than marking individual files or folders as read-only which is what you’re referring to.

The atomic updates but is also pretty stupid, since that’s literally just a process difference,

Yes and no. To get the same behavior without an immutable OS you’d need to take a snapshot before every update and update every package on the system every time and install no additional packages.

and unless you’re running a stock base image (which almost nobody generally is), then you’re not getting full atomic updates globally on your system, and certainly claiming they have no problems is dumb as hell. They then try and point out that NOT being able to update a single application is some sort of benefit, which, hey…maybe that’s subjective, but it’s outright just a dumb claim.

I’m guessing you mean “stock” as in never installing anything additional. If using the base packaging system is your jam then absolutely you shouldn’t use an immutable OS. There are plenty of alternatives to doing a apt install and that’s what you’re encouraged to do because those options don’t usually involve writing to important system dirs.

Lastly, there’s a claim in there seems to sound something like it’s normally a battlefield amongst running applications on a non-immutable system, and that somehow there is problematic interaction between programs which is, again, false and ignorant.

I can’t say I’ve ever run into two packages that, in effect, conflicted with each other, but I’ve absolutely seen packages conflict during installation where I was forced to look for an alternative package without a conflict or complie from source.

Writing “because you’re forced to use containers” doesn’t ring like a feature, so of course they’re going to phrase it the other way.

Saying, “Look at what you can’t do!” is usually not a good idea but depending on your priorities and skill level it’s really about taking riskier options off the table. Yes, some things are more challenging using containers but the likelihood of a container making your machine unbootable is practically zero. I’ve run and administered Linux machines (personally) for over 20 years and not worrying about base packages has frankly been a load off my mind. And because I’m doing more things in containers I’m coming up with solutions I can easily port to any machine.

I would never say immutables are better than standard distros but I don’t think it’s fair to say they don’t provide any advantages or that you can get the same benefits simply by changing your habits.