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

It’s not just a shitty disease…. It’s a shitty disease that the Social Security Administration really, REALLY does not like to pay out disability for. Mostly because, unless something has changed recently, it’s hard to prove that you actually have it because it defies easily quantifiable medical testing, among other things.

So, it would be a curse on multiple levels!

Source: I used to be an attorney who fought for people who had been denied benefits.

I believe the reason a function or method in an object does not need the “function” keyword has to do with the fact that JS is built on the prototype model and the fact that functions are first class in JS.

As the saying goes, “Everything is an object in JavaScript…” (which is not strictly true).

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

Ugh, this is terrible.

Effectively?

Yeah, that’s what it means.

As someone paid to write code that interacts with D365… I see myself in this meme.

I would have loved to see Hemmer mentoring a young Montgomery Scott…

It’s false. Different memory addresses, etc.

I write back end JS, when I’m not writing back end C#.

It’s totally fine. In fact, Node makes it a great back end language. I find that the infamous quirks of JS fall into two categories - “common enough that you internalize the rules for them” and “edge cases that almost never come up in practice.”

And when you write back ends in JS… you aren’t on the endless new framework treadmill!

I maintain that Morrowind has the best lore and main quest story Bethesda has ever written.

Yep, or go proofread some JSON…

I’m sorry, but today is Monday…

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.

This looks pretty cool!

And is only ONE of the reasons Yar’s Revenge is awesome!

Lawful Evil

It’s… fine. Last job was an AWS shop, so I definitely had to learn the differences but all the commonly used stuff is in Azure too.

I can’t really make any legit complaints that don’t exist in AWS in a slightly different flavor.

I’m the “makes commits to Azure DevOps because that’s what his company uses” user, so mine looks a lot like number 4.