Increase your type check strength in 60 seconds!

Lucas Chen on May 24, 2019

Any fool can write code a computer can understand. Good programmers write code that humans can understand. – Martin Fowler There are two guys w... [Read Full]
markdown guide
 

Actually i am not totally agree with that.

The real question behind the == or === is the performance cost.

It is totally legit to think that you can mix both world if you just really improve your performance.

But if the benchmark does not make sens to mix yes it is just an obligation to do that. But... We need that real benchmark :)

 

Using === would always be faster because engine doesn't have to check and convert values to the same type.

 

=== actually does it :). we need real metrics to be sure :)

 

I would say that unless you have hard evidence specific to your application showing that the use of == is faster than === by a statistically significant amount, the problems it introduces are not worth the performance gain, especially during the initial coding phase.

 

i am actually agree but for some type of project or people it does matter :)

code of conduct - report abuse