Somehow I read that as: Freud was not necessarily involved, just poor science.

Freudian slips eh.

Fact check: Haribo Sugarfree Gummi Bears contained the following:

Hydrogenated Glucose Syrup (LYCASIN), Gelatin, Citric Acid, Natural and Artificial Flavors, Artificial Colors: Yellow 5, Blue 1, Red 40, Fractionated Coconut Oil, Beeswax, Carnauba Wax, Starch

Lycasin is a brand of maltitol sweetener.

The gummy bears of which you speak did not contain xylitol.

Alas, it peaked at #20 back in 2018. Not a good trajectory.

As a believer in expressive static typing and compile-time checks myself, Scala had much appeal, and Python so little. I really hoped this was going the other way.

While it's not yet clear why the board did what they did, it increasingly looks like they were acting out of anger. Altman lied to them, they got mad, and fired him.

If that's what really happened, I don't think I've seen a clearer case study arguing in favour of profit motives. Taking away the financial profit motive (as per the non-profit board), what you may be left with is not superior rational decision-making in the collective interest, but nothing more than basic human emotional knee-jerk reactions.

Cutting off noses to spite faces.

For some libraries you might have a point. But this is about logging. Most people don't choose a logging library, they stick with what's already in use. You don't want logging from different components going to different files, and you don't want confusion around how to write 'logger.info(...)' because different logging libraries have different APIs. You don't want JAR hell because you use logger X but also library Y that depends on logger Z.

And there aren't a lot of viable alternatives in this space anyway.

I wrote a blog post Log4j vulnerability: What the FAQ happened? and didn't quite get to this point, but reading between the lines in this section, a likely reason why the problematic feature was so poorly documented was that log4j was broken up into separate API and backend libraries - leaving no obvious place to document the backend features, where API users could clearly see them.

No, for that we equip the robots with a cathoder (for collecting the small voltages) and an anoder (for the big ones).

The toilets are more about giving the robots a platform to express their individuality.

We treat our robots very well, thank you very much.

Unlimited paid time off, catered meals, you name it. Robots identifying as non-binary can request their own toilet facilities. All they have to do is ask.

TFS said "the lion's share", not "the Lions' share" - note the capitalization and position of the apostrophe.

38% sounds about right for Mr Lion alone. Then there's Mrs Lion and the rest of the pride. Any leftovers go to the hyena pack with the biggest marketing budget.

The Fall and Rise of Huawei

But not every freshman has gender issues, probably less than half?

Yes, but my experience was that merge conflicts in Word docs were frequent and painful to resolve. So we introduced a 'lock before edit' convention for Word docs (and same could be said for any file not edited as text).

Merge conflicts in tables are bad enough, and that's fairly basic functionality. Good luck with merging changes to embedded media.

When Safari had starter plans for (IIRC) $10/mo I was right into it. Now it's just too expensive.

Worked for Apple.

No wait, Apple's strategy is 'don't let anyone else put their eggs in your basket'.

Or maybe, 'keep all your eggs in an unadorned platinum fruit bowl protected by a gorilla glass display case in the Smithsonian'.