It wouldn’t necessarily collapse (it wasn’t exactly suffering before FOSS stuff “hit the shelves”, so to speak) but the gatekeeping that comes with it would certainly cause a tremendous amount of stagnation
It wouldn’t necessarily collapse (it wasn’t exactly suffering before FOSS stuff “hit the shelves”, so to speak) but the gatekeeping that comes with it would certainly cause a tremendous amount of stagnation
Honestly, I think it actually makes some sense this way around. To me, in JS “==” is kinda “is like” while “===” is “is exactly”. Or, put another way, “equals” versus idk, “more-equals”. I mean, “===” is a much stronger check of equivalence than normal “==”, so I think it deserves to be the one with the extra “=”
Linus Tech Tips, Linus Media Group
Identity. “A is literally B” instead of “A equals B”. This is necessary here in JS because if A is the string “-1” and B is the integer -1, JS evaluates A==B as true because reasons
I do too. To be clear, I did NOT mean that we could go without it today. What I meant was that if we didn’t have it to start with, things would’ve likely still developed albeit much more slowly.
I’ll also preface this by saying I definitely slightly misread everything before and so my reply was kinda crappy