Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API

From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Search - "ostream would"
-
Why do we post here? Is this just an outlet for our intrusive thoughts? A therapy session for things we can't articulate in meetings? Being able to say controversial things we are not allowed to say other places?
It feels like this place exists outside of time and reality. It really is refreshing, sometimes frustrating, and sometimes really offensive. Things that exist here that would not be tolerated elsewhere:
1. alternate ideas of software, sometimes politics, theories of existence, people liking javascript
2. ostream (I love you man)
3. bullying
4. saying what you really feel
5. telling people to fuck off
What would we do without this place?
Meanwhile my intrusive thoughts:17 -
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!34 -
Chaosesqueteam left.
Nanos left.
Ostream left.
Alexanderr left.
Damn, I wonder how long it would be before I disappear. And how I will be remembered by those who still remain.15 -
So today I got to talking about "plane jacking" with a coworker. To me it has always been called hijacking a plane. I have heard of car jacking though. For some reason plane jacking sounded like masturbation in a plane. Don't know why.
Me: So calling it plane jacking is going to lead to someone attempting to join the plane jacking mile high club and having the toilet damage their penis due to sucking.
Coworker: Nobody is long enough to have their penis reach into there...
Me: I am so sorry. I feel bad for you.
Coworker: ...
Me: That was really good wasn't it?
Coworker: Yeah, but I hate it. <laughs>13