Milky oolong. It has just the right amount of sweetness and just evokes feelings of coziness for me. Sometimes I add a little bit of jasmine as well.

Especially if you didn’t have a lot of spare time. With an active community you can just dip into discussions when you have the time. With a community you’re trying to establish yourself you absolutely have to provide a steady stream of content until it (hopefully) takes off.

The software development industry version of this is “we really need to fix that soon but it’s beyond the scope of this PBI”.

“Soon” is a shorthand for “we’ll put this on the backlog and never pull it into a sprint until it blows up in our faces, at which time we will gripe about how nobody bothered to fix it earlier”.

Exactly. If this was “Marathon: Return to Deimos” or “Marathon: Battleroid Arena” or even “Marathon Infinity Plus One” I wouldn’t complain. Much.

But just taking the name (and logo) of the original one? The game that started Bungie’s path towards being one of the big names of the FPS genre? That’s like saying they went straight from Pathways Into Darkness to Halo. That’s not honoring Marathon, it’s a soulless recycling of an old IP.

My vent cores feel distinctly unblasted.

We know that people have different chronotypes. We even know that most people of working age aren’t really morning people. Unfortunately, our business world assumes a standard circadian rhythm and is structured around getting up early because people needed to use every bit of daylight way back when. So that sucks, especially if you’re an evening or even night person.

Man, I hate it when they make new games that have exactly the same name as an older game by the same company. And this one’s not even a remake. I have no idea if Marathon (1994) and Marathon (upcoming) even play in the same universe but they don’t seem to have much in common gameplay-wise. Ugh.

Makes me wanna install M1A1 Aleph One (didn’t know it does M1 directly these days) and shoot some Pfhor, though.

“You finished a computer game, Atticus.”

The truth was a burning green crack through my brain.

Credits scrolling by, a reminder of the talent behind a just-finished journey. The feeling of triumph, slowly replaced by the creeping grayness of ordinary life.

I had finished a computer game. Funny as hell, it was the most horrible thing I could think of.

There are many OS-related diseases. Many Linux users are affected by or at least know someone who suffers from the compulsive need to mention that they’re using Arch. Then there’s compiler flag addiction, which can develop in Gentoo users. iDependency, the pathological need to purchase any product Apple releases, has financially ruined many macOS users. Windows users’ feelings towards Windows Update and the associated increase in heart rate are known to substantially increase the risk of a fatal heart attack.

Knowing how to operate TempleOS is considered a mental disorder under the DSM-5.

I’d argue that unfun design elements can be useful in games if used with care and purpose. For instance, “suddenly all of the characters you’re attached to are dead” is not exactly fun but one of the Fire Emblem games used it to great dramatic effect at the midway point.

Of course the line between an event or mechanic that players love to hate and one they just hate is thin.

Hoo boy, you weren’t kidding. I find it amazing how quickly this went from “the kernel team is enforcing sanctions” to an an unfriendly abstract debate about the definition of liberalism. I shouldn’t, really, but I still am.

Aw, c’mon! Who doesn’t enjoy piping ten megabytes of JavaScript through Webpack to achieve those crucial on-scroll effects on an otherwise static page?

Speak for yourself. I’m going to migrate all of my 22-bit RSA keys to a longer key length. And not 24 bits, either, given that they’re probably working on a bigger quantum computer already. I gotta go so long that no computer can ever crack it.

64-bit RSA will surely be secure for the foreseeable future, cost be damned.

I also only used v2 but it’s the extra stuff in it that slightly annoys me. Like how turbo mode (brighter than the usual maximum but usually time-limited to avoid overheating) is only available when the full UI is unlocked. Or how there’s a stepped ramp mode that I have to remember to disable whenever I swap out the battery. Or how I can accidentally enter one of the more exotic modes of for some reason I press the button too often.

Anduril is way overengineered. I like this UI that some of my lights have:

While off:

• One push: Turn on at the last used brightness.
• Two pushes: Turn on at maximum brightness.
• Three pushes: That strobe mode that you don’t need but seems to be obligatory.
• Hold: Turn on at the lowest brightness (or moonlight mode if the light has one).

While on:

• One push to turn off.
• Two pushes to toggle between maximum brightness and the last used “regular” brightness.
• Three: That strobe mode that someone has to have some use for.
• Hold: Alternately increase or decrease the brightness.

That’s pretty easy to learn and gives you all the functions you’d reasonably need (plus that strobe) without a lot of clutter.

We used to have one: “Solang das deutsche Reich besteht wird jede Schraube rechts gedreht.” (“As long as the German Empire persists every screw is turned right.”)

Given that the German Empire failed spectacularly, this sentence isn’t very popular anymore.

Pretty much business as usual. Those things pop up every once in a while, which is why Germany has no shortage of experienced bomb disposal experts.

And yes, the fact that this is perfectly mundane is chilling if you think about it. That’s how intensely bombed areas work for decades. Battlefields don’t turn back to normal when the war is over. And we casually do this all over the world for a large number of usually stupid reasons.

I fix that problem by forgetting to turn off Do Not Disturb mode. Also works wonders for blocking all of the calls you do want to take.

They did PR campaigns against Linux and OpenOffice for quite some time – until cloud computing took off and it turned out they could earn more money by supporting Linux than by fighting it.

In fact, Microsoft weren’t happy about FOSS in general. I can still remember when they tried to make “shared source” a thing: They made their own ersatz OSI with its own set of licenses, some of which didn’t grant proper reuse rights – like only allowing you to use the source code to write Windows applications.

True, although that has happened with F/OSS as well (like with xz or the couple times people put Bitcoin miners into npm packages). In either case it’s a lot less likely than the software simply ceasing to be supported, becoming gradually incompatible with newer systems, and rotting away.

Except, of course, that I can pick up the decade-old corpse of an open source project and try to make it work on modern systems, despite how painful it is to try to get a JavaFX application written for Java 7 and an ancient version of Gradle to even compile with a recent JDK. (And then finally give up and just run the last Windows release with its bundled JRE in Wine. But in theory I could’ve made it work!)

Note that this specifically talks about proprietary platforms. Locally-run proprietary freeware has entirely different potential issues, mostly centered around the developer stopping to maintain it. Locally-run F/OSS has similar issues, actually, but lessened by the fact that someone might later pick up the project and continue it.

Admittedly, platforms are very common these days because the web is an easily accessible cross-platform GUI toolkit SaaS is more easily monetized.