723
The Holy Trinity of JavaScript
(programming.dev)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 27 Dec 2023
723 points (98.5% liked)
Programmer Humor
19817 readers
3 users here now
Welcome to Programmer Humor!
This is a place where you can post jokes, memes, humor, etc. related to programming!
For sharing awful code theres also Programming Horror.
Rules
- Keep content in english
- No advertisements
- Posts must be related to programming or programmer topics
founded 2 years ago
MODERATORS
Are people really not using the strict equality operator?
It's still pretty bad that the normal equality operator is as bad as it is.
If you're provided a tool that solves a problem, I don't really get ignoring that and continuing to focus on that solved problem as if it weren't solved because you think all the tools should solve it on principle
That's a little bit like saying, "I don't understand why people continue to complain about the landmine sitting right there on the ground. We've painted it red so you can easily walk around it, so how has the problem not been solved?"
Linters are standard practice in any decent shop. You want to change the language to destroy backward compatibility for one already-solved issue
I think nobody said anything about wanting to fix this. We’re just making fun of how absolutely dumb this is.
Land mines are painted red in my shop. You want to change the language to remove a land mine that everyone competent already knows enough to step around. The problem has already been solved, so why are you continuing to complain about it?
Just to be clear, I'm not actually calling for JavaScript to change, I'm just pointing out that people are right to point out this as being a problem. Having said that, if everyone competent uses linters now so that this feature isn't used in practice anymore, then getting rid of it shouldn't even break anything, and arguably code which would break is already broken because it uses an operator that no one should be using, so you shouldn't be using this code anyway.
Using linters in a professional setting is more like moving all your actual employees into a different office and letting them use robot avatars in the original office who can never step on that landmine.
The benefit of this is that millions of other robots continue to depend on the original office being exactly as it is and many of them will never change or update, nor is their any need for them to.
Breaking backwards compatibility on the web needs much better reasoning than 'I don't want to use a linter'.
I can sort of get down with what you're saying, but on the other hand, we all have design constraints, inside and outside of programming, I think this is a very minor one
Sure, but it is also a very gratuitous and pointless design constraint.