sproingie

I dunno, there was also awarding the Peace Prize to Kissinger…

It’s a cheeky way of saying that the punctuation is doing a lot of work in making the phrase understandable.

Emacs keybindings are even baked into NSText, the basis of everything to do with text handling in macOS.

Sure, the average container in fact brings along an entire OS distribution like Alpine or Ubuntu or whatnot, but there’s still no extra layers added (save perhaps for the filesystem). Then again, running an OS at all is not “bare metal” by some definitions… it’s all various amounts of alloys I suppose.

A container is simply a process with isolated namespaces — an OS does not run within them, and any hardware access they have is mediated by the OS in the same way as any other process. This being from Linux’s POV anyway: once you’re running Docker on other OS’s, there’s a Linux VM in the middle.

Plus Atlassian is kind of just an awful company.

How so?

Why would you even dump your loot in Borderlands? Money is absolutely meaningless in that game. You look at the comparison box to see if there are more green arrows and if not you leave it.

I have been writing JavaScript since JS has existed, and the One Weird Trick I learned to working with JS’s OO system is to use it as little as possible. Don’t get me wrong, objects are wonderful, but you don’t need JS’s barking insane semantics around “this” when static closures work fantastically. It’s not even the prototype model that I’m talking about, it’s having to do things like foo.bar.bind(foo) or having to know that an event handler will re-bind “this” and so on. The Vue and React communities have caught on to this, and writing code for those is so much more pleasant now that there are fewer land mines like that to step on.