add that and that and that, put that out, and in the end we understand the final conclusion will not satisfy most people and we will not put all the options everybody wants, so we don’t put anything. In the end, strict mode is a reasonable compromise.
I think this statement really expresses the logical extreme of the "yes to each no to all" problem, by defaulting to "no to any" unless there's good enough reason to believe a particular change is without doubt the right decision for the language. And having used both Lua (mostly privately) and Ruby (mostly for work), I really do like how the language stability leads to a very concise and reasonable design. Ruby, for all its cool features, is also stuck with more than a few "legacy" features that turned out to not be as good a choice as it seemed at the time, despite being somewhat picky about what features to add:
The most popular question is: "I’m from the language X community; can’t you introduce a feature from the language X to Ruby?", or something like that. And my usual answer to these requests is… "no, I wouldn’t do that", because we have different language design and different language development policies.
—Yukihiro Matsumoto, in a recent interview
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Schools really should put more emphasis on teaching basic logic causalities like this.
As for the main point of the article; I think a good example of avoiding this effect is Lua.
Quoting Roberto Ierusalimschy:
I think this statement really expresses the logical extreme of the "yes to each no to all" problem, by defaulting to "no to any" unless there's good enough reason to believe a particular change is without doubt the right decision for the language. And having used both Lua (mostly privately) and Ruby (mostly for work), I really do like how the language stability leads to a very concise and reasonable design. Ruby, for all its cool features, is also stuck with more than a few "legacy" features that turned out to not be as good a choice as it seemed at the time, despite being somewhat picky about what features to add: