that moment you fix the bug that was unfixable

That moment when you clean the cache on android phone with 4GB every time you want to download a new app, even if you have 32GB sdcard
😱😱😱

I want to explain to people like ostream (aka aviophille) why JS is a crap language. Because they apparently don't know (lol).

First I want to say that JS is fine for small things like gluing some parts togeter. Like, you know, the exact thing it was intended for when it was invented: scripting.

So why is it bad as a programming language for whole apps or projects?

No type checks (dynamic typing). This is typical for scripting languages and not neccesarily bad for such a language but it's certainly bad for a programming language.

"truthy" everything. It's bad for readability and it's dangerous because you can accidentaly make unwanted behavior.

The existence of == and ===. The rule for many real life JS projects is to always use === to be more safe.
In general: The correct thing should be the default thing. JS violates that.

Automatic semicolon insertion can cause funny surprises.
If semicolons aren't truly optional, then they should not be allowed to be omitted.

No enums. Do I need to say more?

No generics (of course, lol).

Fucked up implicit type conversions that violate the principle of least surprise (you know those from all the memes).

No integer data types (only floating point). BigInt obviously doesn't count.

No value types and no real concept for immutability. "Const" doesn't count because it only makes the reference immutale (see lack of value types). "Freeze" doesn't count since it's a runtime enforcement and therefore pretty useless.

No algebraic types. That one can be forgiven though, because it's only common in the most modern languages.

The need for null AND undefined.

No concept of non-nullability (values that can not be null).

JS embraces the "fail silently" approach, which means that many bugs remain unnoticed and will be a PITA to find and debug.

Some of the problems can and have been adressed with TypeScript, but most of them are unfixable because it would break backward compatibility.
So JS is truly rotten at the core and can not be fixed in principle.

That doesn't mean that I also hate JS devs. I pity your poor souls for having to deal with this abomination of a language.

It's likely that I fogot to mention many other problems with JS, so feel free to extend the list in the comments :)

Marry Christmas!

programmer's nightmare, dreaming about unfixable bugs

Today I fucked Up by making friend install Linux when he doesn't even know what OS is.

Friend's Windows 7 broke. Unbootable & unfixable. I told him to reinstall. He has no idea how so he told me he will rent a PC (apparently that's a thing) until he buys a new one (he wanted it anyways). I told him it's bullshit to rent for PC when yours is totally ok only without OS.

He agreed and that's where I fucked Up. I told him how to make bootable flash disks(it was pain to get some info from him tho..) and he said he downloaded cracked Win7.. I told him it's suicide to use cracked OS for MANY fucking reasons. He agreed and I told him to install Ubuntu.... I thought it's easy that even my grandma could use it...... Well, apparently I was, in technical terms, "FUCKING WRONG"(all caps cuz tech terms).

He wasn't even able to Google how to install Steam on Ubuntu(apt install steam?) ... Constantly asking me "well and what should i write to Google?" And other shit..

I Always woke up to messages From him like "This shit doesn't work I'mma uninstall it" and I Always responed in one command or first Google result and it suddenly started to work.

After 2 days he gave up and is using cracked Win7. Can't wait for his reaction when I pwn him on nearest LAN party 😂 Maybe he will reconsider using cracked OS.

Anyway I learn from my Mistake. Just fuck me...

every bug is a feature if it is unfixable enough

I'm so frustrated right now.
I put a lot of effort in a (voluntary) web project where its main component is based on a html table. Everything tested in dev (Chrome, FF), demo deployed and now I open it in Safari (macOS) just to discover that the rendering is broken. A Google search revealed some people with similar problems and many unanswered StackOverflow questions. It's unfixable.
Why Apple? Even MS got its sh** together.
It's unpaid work... I just wanted to something good.

Great feeling when the pen testers couldn't find the "unfixable" vulnerability your new feature created, and you go on holiday soon.