I’d argue that it’s Android’s DE for Linux.

Works fine for me. ¯\_( ᵔ ~ ᵔ )_/¯

A colleague always complains that KDE looks like Windows. She does also get jealous, though, when she sees me using poweruser features.

I just ate wholemeal rice and still would not have guessed rice. 🥴

I was overplaying it for comedic effect. 🙃

My mum makes fruit salad with oranges, apples, bananas and then adds in apple juice to make it blend well.

To be honest, I’ve noticed that with lots of foods. I know what the thing looks like in stores, but I have no idea what it’s like in nature.

Cashews were another recent one, where I never would have guessed what they look like:

Excuse me, it’s smoothies that are an abomination, if anything.

You’ve got beautiful fruit where each bite tastes and feels different, which have long fibers with structural integrity to prevent your stomach from ingesting the sugar all at once, and then you decide:
Nah, I’d rather have fruit soup, where the whole thing just has a singular monotonous taste. And where there’s nothing to chew. Just sign me up for the retirement home now.

I believe, it’s a US thing. This is a quote from the official Dietary Guidelines for Americans (DGA):

Other Vegetables: All other fresh, frozen, and canned vegetables, cooked or raw: for example, asparagus, avocado, bamboo shoots, beets, bitter melon, Brussels sprouts, cabbage (green, red, napa, savoy), cactus pads (nopales), cauliflower, celery, chayote (mirliton), cucumber, eggplant, green beans, kohlrabi, luffa, mushrooms, okra, onions, radish, rutabaga, seaweed, snow peas, summer squash, tomatillos, and turnips.

Source: https://www.dietaryguidelines.gov/sites/default/files/2021-03/Dietary_Guidelines_for_Americans-2020-2025.pdf (page 28)

I’ve read elsewhere that the reason for the DGA to conflate them, is because mushrooms have comparable nutrients to vegetables. So, from a dietary and regulatory viewpoint, it makes some amount of sense. But yeah, I feel like you could have just had a category “vegetables & mushrooms”.

There’s no way they actually checked that it works. It includes code for:

• XDG
• GNOME
• “GNOME_old”
• KDE

Verifying this would mean logging into several different desktop environments.

It’s also extremely fragile code, running external commands and filtering through various files. There just is no good API on Linux for querying whether the desktop environment is using a dark theme, so it’s doing absolutely inane shit that no sane developer would type out.

Because it’s a maintenance nightmare. Because they almost certainly don’t actually need to solve this. That’s software development 101, to not write code that you don’t actually need. But apparently some devs never got the memo that this is because of the maintenance cost, not because you weren’t able to generate the code up until now.

You not using any libraries? We have like 1100 animals in our software at work (that we know of).

I think, their point (and also my experience) is that you get taught about it in university a lot more than about simple loops, so it feels more important even though you rarely use it in reality.

Same thing goes for linked lists and inheritance…

I’ve heard before that people feel good on a carnivore diet at first, but then it flips into the negative pretty quickly as your body runs out of vitamins.

Wikipedia lists even more drastic long-term problems: https://en.wikipedia.org/wiki/Carnivore_diet#Health_concerns

Maple syrup could have worked. But yeah, it’s often also worth changing up plans, like maybe just roast the nuts as well and put them on top with some chives or balsamico creme for the looks. Of course, I don’t know what kind of constraints you’re working with, though…

For me, it helped expand my cosmos by leaving things out and looking for alternatives.
Like, I found out about a world of legumes by going vegan. And earlier this year, I stopped eating wheat for health reasons, and only then started to appreciate the existence of millet, quinoa, amaranth, buckwheat etc…

I am probably still within the range of “usual” foods, all things considered, but at least I’m breaking out of a tiny subset of those…

Yeah, I’m not saying that the term is well-defined or that some usages of the word don’t typically refer to classical algorithms after all.

And yes, obviously even the currently trending meaning of what “AI” might mean, i.e. generative AI, still involves lots of algorithms, for training, for executing the model, and tons of auxilliary scripts that ideally take over all tasks as soon as the statistical model has decided what to do.

And yes, maybe non-techies really just don’t care. My post wasn’t supposed to be snide commentary on that. It was more just an “oh fuck, there’s folks that hand out bags of money solely based on whether a program uses a butthole as a logo and says that it’s thinking for its loading times”.

Oh man, I fear that this is genuinely what lots of people take as their clue as to what’s AI and what is not. I’ve seen plenty people refer to algorithms as AI. They’re probably wondering why this AI is so reliable compared to the others…

But what if it’s the liquid that remains after you’ve washed up?

I do enjoy how many number sets are referred to as “normal numbers”:

• Natural numbers
• Rational numbers
• Real numbers
• “Integer” is Latin for “hasn’t been fucked with”
• And of course, the most normal numbers: https://en.wikipedia.org/wiki/Normal_number

A rebase rewrites the history of your branch, so that it’s as if you just branched off and then coded all your changes in one sitting.

It will go through each of your commits and try to apply them one after another. If something changed on the base branch that conflicts with your changes, it will prompt you to adjust your commit. You adjust it so that looks as if you just coded it on top of the base branch.

When you have lots of commits on your branch, this can mean that while you’re rebasing, you have to then also change your following commits which happened to touch the same lines as a previous commit. This can mean additional, stupid work.

As such, a workflow using rebases (“trunk-based workflow”) works best, if you can rebase often and merge back early. You won’t get merge conflicts when merging back, nor merge commits, because you resolved these while rebasing.

In particular in smaller teams where you have tight-knit communication, this workflow is absolutely stellar. It completely bypasses so many pain points that folks have with Git.
Merge conflicts are significantly reduced when you merge often and a trunk-based workflow removes the ceremony that typically prevents teams from doing just that.

Typically, touchpad gestures (particularly multi-touch gestures) will work better on Wayland, because it has libinput.