“approximately equal” doesn’t make sense in coding as a syntactic operation, so there’s not much of an ability to cause misconception nor is there a demand to make it != simply because other programming languages do it. there are also programming languages that do <>, you wanna ask them to change too or should we fit them?
where’s the lazy part about this? they gave a perfectly valid reason why they would not implement this.
1 Like
Check their bio, I think it’s ragebait
Genuinely not rage-bait. Seems like they did put some thought into it, so I guess you could argue it’s not lazy if the conclusion is that it degrades the experience. Personally I see it as a slight polishing improvement that might not be worth the slightly added complexity.
Not lazy, maybe just boring 
Maybe I’m just lashing out because everyone’s dunking on my brilliant idea 
That was not their main point. They are not adding it because there is no given reason for it to be implemented other than “it’s in other languages”, it doesn’t make code shorter, it adds no additional functionality, and could also limit how future syntactical features could be implemented [paraphrasing what Yuria said]
this is from the big man Arseny Kapoulkine himself
(ah yes, incorrectly using the word esoteric while complaining about reading a single page of text… maybe past me is rage baiting present me)
prior to your post right here, there is literally zero mention of this response on some Github discussion about it within this thread. Everyone here is commenting purely on the staff response in this thread. where they gave an incredibly understandable explanation on why they decided against this feature.
1 Like
That’s great and all, thanks for stating the obvious, but I’m not trying to argue with you. I’m adding additional context. This post has gotten too toxic for me. I’m going to try to stop replying. Thanks.