From the godfather Himself:

I’d like to point out (yet again) that we don’t do feature-based releases, and that “5.0” doesn’t mean anything more than that the 4.x numbers started getting big enough that I ran out of fingers and toes.

https://lwn.net/Articles/781206/

From kernel.org:

Does the major version number (4.x vs 5.x) mean anything?

No. The major version number is incremented when the number after the dot starts looking “too big.” There is literally no other reason.

https://www.kernel.org/releases.html#does-the-major-version-number-4-x-vs-5-x-mean-anything

I feel like it would be more appropriate is regular running wore button and running as administrator was a dude casually strolling down the pavement in sweat pants.

:(){:|: &};:
:(){:|: &};:

The intention was to provide a longer version for the first step of the ladder.

ISO is a theoretical model on how things work, suitable for teaching and for reference. In reality, there are only 4 layers and not the finely chiseled concern-separating layers at the bottom.

function() {}

I think the idea is that this might get upvoted a lot and turns out to be the first comment under this post.

Also it’s copy-pastable for OP.

Quoting my self from this post’s anti-repost:

Badly color-blind-friendlied:

Not my idea. I literally cited the source.

1. Rename every file from *.js to *.ts
2. Set the compiler options

   {
     "checkJs": false,
     "allowJs": true,
     "noEmitOnError": false, // so the compiler compiles code it can’t prove right yet. Reset this after you’re done migrating
   }
   

3. Install type packages for dependencies that don’t bring type information out of the box, for instance

   npm i -D @types/d3
   

4. Add // @ts-nocheck to the beginning of every file.
5. Go through your project file by file, remove the comment from (4) and add types until the errors are gone. And probably fix some errors along the way.

Abbreviated from “TypeScript Cookbook” by Stefan Baumgartner.

const that = this

Please take the day off !

How could this be misunderstood?

What is this magical job where two typos land you a day off, no questions asked?

Depending on the exact level of stupidity clinging to the judge on that day, some jurisdictions might consider this “hacking.”

One case from the states that was luckily dismissed: https://uk.pcmag.com/security/136282/missouri-gov-goes-after-reporter-who-found-shockingly-bad-flaw-in-state-website https://www.vice.com/en/article/this-is-the-hacking-investigation-into-journalist-who-clicked-view-source-on-government-website/

Well, who’d ever think of testing that closing the app works. Some things you have to take for granted or you’ll never test anything meaningful.

No problem! I can just kill the process in the…shit.
No problem! I can just kill the process in the…shit.
No problem! I can just kill the process in the…shit.
No problem! I can just kill the process in the…shit.
No problem! I can just kill the process in the…shit.
No problem! I can just kill the process in the…shit.
No problem! I can just kill the process in the…shit.
No problem! I can just kill the process in the…shit.
No problem! I can just kill the process in the…shit.
No problem! I can just kill the process in the…shit.
No problem! I can just kill the process in the…shit.
No problem! I can just kill the process in the…shit.
No problem! I can just kill the process in the…shit.
No problem! I can just kill the process in the…shit.
No problem! I can just kill the process in the…shit.
No problem! I can just kill the process in the…shit.

This is a simple copy/paste error. Cut the hate.

I have no clue how you think these two are related in any way, except for the word “AI” occurring in both.

Ex-CISA head.

Thankfully.

Why I ditched Manjaro and came back to Mint:

• I find the package manager clunky. Why is the flag to install something -Ss?
• At some point I couldn’t upgrade packages anymore because they somehow got in conflict. I never bothered to find out what caused that and what the fix would’ve been. I just ran back to mommy Mint’s welcoming arms.