I chose the middle option for things I’m not hosting, but could see myself hosting in the future.

The worst part about quadlets, IMO, is that they don’t use the same key words as podman run does. So turning a working podman container into a quadlet can be challenging.

I’m in a similar boat. The difference for me is that I can definitely tell times where I’m faster. But there are still times where I fumble around. I know that eventually, I’ll be way faster using vim motions than I ever was without them.

When I first started actually trying to use it to do work, it felt pretty bad. But once I got over the hump it felt better.

I think I’m at the point where I’m at least as fast as I used to be, if not slightly faster.

The ease of switching really just depends. Myself, I’ve had several stumbles switching, but I’m still so happy I did and I’m not going back. My wife on the other hand, has had no issues switching from her Chromebook, because she’s a super basic user who spends all her time in the browser.

Check out Tailscale. It uses Wireguard under the hood, but it’s magic.

containers should be immutable and not be able to write to their internal filesystem

This doesn’t jive with my understanding. Containers cannot write to the image. The image is immutable. However, a running container can write to its filesystem, but those changes are ephemeral, and will disappear if the container stops.

There’s a good deal of misinformation here. The main part being disk space. While it is true that flatpak apps will take up more space, it’s not nearly as bad as you think it is. There is a lot of really good optimization going on under the hood that you don’t see. Dependencies are de duplicated. I’m no expert on it, but I believe that dependencies also have delta changes from one version to the next.

Regarding apps not supporting building of the source, you should get over that or do the work of supporting it yourself. Open source is a hard, usually thankless job.

For me the problem is that he LARPs as Tony Stark and idiots but into it. He pretends to be a smart engineer when he lucked into all of it and is really not all that bright.

People love to prove how “smart” they are. It’s extremely reliable.

I unfortunately still mindlessly scroll Facebook when I’m bored. When I see some kind of obvious rage bait, people will trip over themselves to comment about it, even if a thousand other people have already said what they came to say.

The kind of things I’m taking about are like this. Completely mispronouncing a common word in every single video. The kind of word that no one ever mispronounces. Or someone opens their refrigerator to get something out of it and there’s random items conspicuously placed in it that obviously didn’t belong there.

The kind of things that anyone with half a brain knows is purposefully done. And yet thousands of people will shit themselves trying to get the comments opened so they can correct the record.

Because it’s in the public’s interest.

Cast iron for sure works and I’m pretty sure carbon steel does, too. If a magnet sticks to it, it works.

They are garbage for heat control if you use them the same way you would a gas or induction stove. If you learn how to use one, resistive electric stoves cook just fine.

You like using cheap aluminum pans?

Nobody here wants you dead

This is a lie or willful ignorance.

It’s a contracting agency. Not individual contractors. Unfortunately we have lots of rubber stampers on our team who approve code while you’re not looking. And let me be clear, we have on shore who contribute awful code, too.

It’s all a mess.

Our off shore contractors produce some of the worst code. But it’s impossible to get work done and also be vigilant enough to reject their bad pull requests. So basically you’ll end up looking a code one day that is godawful and think, “this is off shore”. And yep, git blame tells you you’re right.

So, slightly tangential, but I have a failed home automation project this past week.

I have been using an unofficial integration for my mini-splits for a few years. The guy who wrote it likes to disappear for 6 months at a time and it seems like it may be abandoned. It finally stopped working after a home assistant update.

I had bought some ESP based replacement dongles about a year ago and decided to finally use them. Well, not all of the features worked, so I set about writing my own firmware.

That ended up working even less well. I wasted a lot of time and effort trying to get my firmware to work before giving up and just moving to the fork of the original Home Assistant integration for the official dongles.

I hate being beholden to third party stuff like this because I have robust automation setup for my mini-splits and updates can completely break them and be a massive pain to fix.

I’m not sad I tried and failed so much as I’m just sad it didn’t work. I may try again sometime in the future.

The fucking Okta verify app and its “cannot find trusted route to whatever” error popup that covers the approve button that cannot be dismissed except for just waiting for it to go away. Love that.

Oh! I finally got tired of swiping away the “setup express login” or whatever they call it and set it up. It’s not any fucking faster! In fact, it’s slower! It’s the same process, but now I have to also use my fingerprint at the end. And there’s enough of a lag that I often forget I have to do that so I’m starting at the login screen waiting for the approval to go through.

And, I have to use the thing twice to get on GitHub or the corporate VPN. It is so fucking tedious and stupid.

I prefer Podman. But Docker can run rootless. It does run under root by default, though.

No reason you can’t use NixOS in a VM on Proxmox.

My container host OS is another immutable, uCore, which I run in a VM on Proxmox.