Though, obviously I had to come up with some ridiculous solutions:

bool IsEven(int i) => ((Func<string, bool>)(s => s[^1] == 48))($"{i:B}");

This one works without conditionals :)

bool IsEven(int i)
{
    try
    {
        int _ = (i & 1) / (i & 1);
    }
    catch (Exception)
    {
        return true;
    }

    return false;
}

Not to take from all the funny answers … but

bool IsEven(int i) => (i & 1) != 1;

(C#)

I like to style visited links blue and unvisited links purple, just to mess with people.

That’s ok, we don’t kink shame around here.

Breaking Bad and Avril Lavigne in one meme about linux vs windoze … what a ride …

To every arch meme action, there is an arch user overreaction.

It’s what makes it fun.

A fucking sexy security hazard.

I just had to imagine you facing the fedora installer’s partitioning tool:

Whoever made this eons ago was a genius.

https://youtu.be/kNUmQj_7ajU

;-)

Too much to type and may prompt you if you’re sure. Just go with

\rm -rf /*

Well, not by accident.

I just dabbled in javascript again, and that description is spot on!

console.log(‘javascript operators are b’ + ‘a’ + + ‘a’ + ‘a’);

I am. A lot of people fail to see that.

OK commie.

Almost looks like something taken from ASL linux.

OK luddite.

That’s a nonsense spin of things. There wasn’t/isn’t a need for Microsoft to push systemd, because it had been adopted by all major linux distributions before Poettering even made the switch. It’s a straw that init system luddites clutch at.

I’d like to propose a new rule for this community:

People criticizing systemd to the extent where they promote alternatives (regressions), have to provide proof that they have or are maintaining init scripts for at least ten services with satisfying the following conditions: said init scripts must 1.) be shown to reliably start up the services and 2.) not signal their dependencies to early and 3.) gracefully stop the services 99.9% of the time. People failing to satisfy these conditions are not allowed to voice their opinions on how arbitrary init systems are better than systemd. Violations of this rule will be punished by temporary bans and forcing the violators to fill the entire canvas of a blackboard with “‘do one thing and do it well’ is a unix principle, not a linux principle” in fine print.

More lines of semi-reliable init scripts have been written by package maintainers, than lines of systemd code by Poettering & Co, and that while achieving far less. The old init systems might have been simple, the hell of init scripts wasn’t.