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.

[–] masterspace@lemmy.ca 1 points 10 months ago* (last edited 10 months ago)

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'.

[–] TrickDacy@lemmy.world -2 points 10 months ago (1 children)

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

[–] bitcrafter@programming.dev 2 points 10 months ago

Sure, but it is also a very gratuitous and pointless design constraint.