Subtitle: An Autobiography

If only there were some easily identifiable common denominator…

Hopscotch

Did you leave it in your car?

My YouTube account is old enough to vote at this point…

The real question is…. WHY DOES AZURE DEVOPS STILL EXIST?!?!?

Personally, I use the very technical method of listening for the buzzer to go off…

I hate that everything has WiFi for no reason…

“Kirk to Enterprise…”

That’s kind of what the ublue project is doing. Bazzite is a part of that, of course. But it also has more “normal” versions like Bluefin (gnome) and Aurora (plasma).

You know all those Cyberpunk books and movies?

Apparently we thought those were a suggestion instead of a warning…

I mean, that’s what the marketing folks at the hyperscalers would have us believe…

Yep. I’ve also used a paper clip, straightened out with a very small bend at the end.

I’ve also used chewing gum, though you have to wait it for it to harden a little. Duct tape might work too.

You only have to get it to move out a tiny amount. Then you can get a pair of needle nose pliers on it and pull it out.

That particular key looks challenging though.

Amen

I assume you mean fascist propaganda over and above the right wing rabbit holes that already exist on YouTube….

Ugh, this is terrible.

Yes! This what I usually do. I will develop on the host using tools installed via Homebrew, then package/build/test via docker.

And to be clear, I really love the ideas behind Bluefin and use it every day. I’ve just kind of given up on devcontainers, specifically.

Honestly, even with VSCode, devcontainers are kind of just ok, at best.

They are very fiddly. The containers keep running when you close VSCode (which makes sense, and sure the resource usage is minimal, but it’s damned annoying) and you have to stop them manually. Meanwhile the commands in VSCode to work with/activate the containers are not super clear in terms of what they actually do.

Oh, what’s that? Need a shell inside the container you’re working in for testing things out, installing dependencies, etc.? Well, I hope you pick the right one of VSCode’s crappy built in terminals! Because if you want to use a real terminal, you are stuck with the crappy devcontainer CLI to exec into the container. A CLI that is NOT up to date with, or even includes, all the commands for devcontainers in the editor (which is what makes working with them in other IDE/editors such a pain in the butt…).

And this gets me…. What? A container I can share with other developers, sure, but it’s very likely NOT the container we are actually going to deploy in. So…

Yeah, I’ve also had a lot of frustrations with devcontainers in Bluefin. I really like what the Bluefin project is doing. The reasoning behind it makes a lot of sense to me. But devcontainers are kind of pushed as the way you “should” be writing code on Bluefin and it’s…. not great.

They do have Homebrew and Distrobox though, which helps a lot. I have ended up doing most of my development work on Bluefin on the host system with tools installed via brew, which is kept separate enough from the rest of the file system to still keep things tidy.

Overall, I think Bluefin is great and it, or something like it, may very well be the future of Linux… but the future isn’t here just yet and there are some growing pains, for sure.

Lawful Evil

I second this one. LEGO is really well made, the sets are well designed, and the instructions are some of the best you’ll ever see in any build-it-yourself product of any kind.

Well, the bar was low…

I agree, but knowing it’s from Norway makes me feel more comfortable with the idea of using it than if it was made in the US…. (And I’m American…)