You did 200k years. You need to do 200k years as seconds (the 6.311e12 they mentioned). Their math is right.

Not sure why you’re acting like they claimed to invent the logarithm, either…

There’s already a ton of such exploits. Most servers use Linux and many exploits of corporations this had to go through Linux (though many exploits aren’t related to the OS at all – eg, SQL injection is OS independent). I expect it’s more common, though, that attacks on Linux systems are either meant to target servers or were personalized attacks that you’re not gonna accidentally download.

On that vein, I also kinda suspect that many people who use Linux may be bigger targets for their employer than their personal PC. Which is actually scary, cause personalized attacks are far harder to defend against. I expect the average Linux user is technically savvy. Not a lot of money in try to do a standard, broad attack on such types (I think most attacks on personal computers are broad attempts that mostly depend on a small fraction of technologically incompetent people falling for simple schemes). But a personalized attack that happens to infiltrate a fortune 500 company? Now that’s worth a lot of money. Using Linux won’t protect you against those kinda attacks.

Some of these I get, but I don’t get the T9 thing. T9 was so bad! It took ages to type many words. Today’s predictive keyboards are miles better.

Also, no software updates? Sure, every now and then there’s a shitty update, but most updates are great. New features and especially bug fixes are amazing. Used to be that if something had a bug, you just had to deal with it. There’s no guarantees it’ll be fixed today, but many companies do fix their bugs at least eventually. The ability to iteratively develop is huge for software quality. These days, unless you’re developing something that absolutely cannot fail (like a mars prober or radiation therapy machine), it’s widely agreed upon that iterative design is superior to “waterfall” design of trying to plan it out all ahead of time. Part of why is so you can get feedback continuously instead of only after you’ve committed to months of tech debt.

Ugh, there’s some parts of YAML I love, but ultimately it’s a terrible format. It’s just too easy to confuse people. At least it has comments though. It’s so dumb that JSON doesn’t officially have comments. I’ve often parsed “JSON” as YAML entirely for comments, without using a single other YAML feature.

YAML also supports not quoting your strings. Seems great at first, but it gets weird of you want a string that looks like a different type. IIRC, there’s even a major version difference in the handling of this case! I can’t remember the details, but I once had a bug happen because of this.

Performance wise, both YAML and JSON suck. They’re fine for a config file that you just read on startup, but if you’re doing a ton of processing, it will quickly show the performance hit. Binary formats work far better (for a generic one, protobuffers has good tooling and library support while being blazing fast).

Let’s not pretend people acknowledge warnings, though. It’s a popular meme that projects will have hundreds of warnings and that devs will ignore them all.

There’s a perfectly valid use case for opinionated languages that don’t let you get away with that. It’s also similar to how go has gofmt to enforce a consistent formatting.

Honestly, I’ve been using Go for years and this unused variable error rarely comes up. When it does, it’s trivial to resolve. But the error has saved me from bugs more often than it has wasted my time. Most commonly when you declare a new variable in a narrower scope when you intended to assign to the variable of the same name (since Go has separate declare vs assign operators).

For today’s 10,000 who have never seen it, https://xkcd.com/936/ succinctly explains why the whole mixed character types thing isn’t favoured.

“I use Linux as my operating system,” I state proudly to the unkempt, bearded man. He swivels around in his desk chair with a devilish gleam in his eyes, ready to mansplain with extreme precision. “Actually”, he says with a grin, "Linux is just the kernel. You use GNU+Linux!’ I don’t miss a beat and reply with a smirk, “I use Alpine, a distro that doesn’t include the GNU coreutils, or any other GNU code. It’s Linux, but it’s not GNU+Linux.”

The smile quickly drops from the man’s face. His body begins convulsing and he foams at the mouth and drops to the floor with a sickly thud. As he writhes around he screams “I-IT WAS COMPILED WITH GCC! THAT MEANS IT’S STILL GNU!” Coolly, I reply “If windows was compiled with gcc, would that make it GNU?” I interrupt his response with “-and work is being made on the kernel to make it more compiler-agnostic. Even you were correct, you wont be for long.”

With a sickly wheeze, the last of the man’s life is ejected from his body. He lies on the floor, cold and limp. I’ve womansplained him to death.

his disdain for the poors.

Correction: his disdain for everyone who isn’t himself. He doesn’t even treat his own kids well. His trans daughter changed her name to not be associated with him.