Learn More
Resend Email
6
hinst
3y

Not gonna lie; having both != == and !== and === in JavaScript is one of the most stupid bad design moments; in my opinion.

I am not even going to bother trying to come up with a better syntax for that. I will never get over how bad it is. So bad. === is 🤡

random

js

javascript
Favorite
Ranter
Comments
  • 5
    3y
    I agree.

    Objects should implement their own comparators for truthy/falsy values.

    Honestly, ‘.empty?’ would cover most of these: [] {} “”
  • 3
    3y
    @Root except "truthiness" of objects and arrays is not based on whether or not they're empty. `!= null` would cover those.
  • 0
    3y
    @localpost Yeah, I know. JS is a mess.
  • 2
    3y
    What do you expect from language that was written in 10 days?

    not much!
  • 1
    3y
    In PHP is even worse.
  • 0
    3y
    It's a symptom of the insanity inherent in JS rather than a bad idea in itself, I guess. I've never really had much cause to use the strict comparators outside of a linter reprimand, you just get used to working around JS's uh 'type system'
  • 1
    3y
    JavaScript and css have a lot of gotcha stupid rules that I tend to forget. You have to (sadly) commit a lot of these dumb rules to memory
  • 1
    3y
    JS board meeting: Make sure you add extra simbols in the syntax. Developers love that shit!
Related Rants
devRant © 2021 Hexical Labs LLC
Privacy Policy  |  Terms of Service
Add Comment