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?”
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.
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
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’.
What’s especially wild to me is that even the position of “it’s ambiguous” gets almost as much pushback as trying to argue that one of them is universally correct.
Last time this came up it was my position that it was ambiguous and needed clarification and had someone accuse me of taking a prescriptive stance and imposing rules contrary to how things were actually being done. How asking a person what they mean or seeking clarification could possibly be prescriptive is beyond me.
Bonus points, the guy telling me I was being prescriptive was arguing vehemently that implicit multiplication having precedence was correct and to do otherwise was wrong, full stop.
Without any additional parentheses, the division sign is assumed to separate numerators and denominators within a complete expression, in which case you would reduce each separately. It’s very, very marginally ambiguous at best.
👍 That was actually one of the reasons why I wrote this blog post. I wanted to compile a list of points that show as clear as humanity possible that there is no consensus here, even amongst experts.
That probably won’t convince everybody but if that won’t probably nothing will.
When I went to college, I was given a reverse Polish notation calculator. I think there is some (albeit small) advantage of becoming fluent in both PEMDAS and RPN to see the arbitrariness. This kind of arguement is like trying to argue linguistics in a single language.
Btw, I’m not claiming that RPN has any bearing on the meme at hand. Just that there are different standards.
Ambiguity is fine. It would tedious to the point of distraction to enforce writing math without ambiguity. You make note of conventions and you are meant to realize that is just a convention. I’m amazed at the people who are planting their feet to fight for something that what they were taught in third grade as if the world stopped there.
You’re right though. We should definitely teach different conventions. But then what would facebook do for engagement?
I think there’s a difference from the doom and gloom of your post and the actual problem. Quick generated-spam content is really what you’re arguing against.
I can see the use of well crafted jokes in the form of AI art being acceptable. I do not like low-quality spam content though.
I think it’s too rash to just say “ban AI content” and instead reinforce rules like “Ban low effort posts/comments”. The AI stuff that’s low quality farming has been pretty obvious.
programming.dev
Top