4 ms·
Only one of those solutions has negative ever-lasting effects though and a bad name definitely does break things. A broken app can be fixed once, by one develo
by hungerstrike 9y ago
Only one of those solutions has negative ever-lasting effects though and a bad name definitely does break things.
A broken app can be fixed once, by one developer. A bad name will cause confusion among all developers and waste their time.
Unfortunately, JS already has such shitty names for things that everybody just accepted this. But, they were wrong. They should have definitely broken apps built with mooTools because of the reasons that I stated and also since browsers have already broken tons of sites for lesser reasons such as removing ads.
- woah 9y agoJS prioritizes backwards compatibility to a very high degree. This has proven to be a strength over the years, as it allows the language to evolve quickly without big drama like python.
- namelost 9y agoIt's not comparable with Python, which broke correct code to the point where even `print "Hello world"` was broken! This mootools issue only affects a very small number of users. It amounts to a denial-of-service attack against the language, if you author a popular enough JS library you can screw things up for everybody in perpetuity. That isn't a healthy way to design a language.
- a_humean 9y agoGive the guy a break, he was given 10 days to design the thing. It worked out pretty well in the end. This is spilt milk from 20+ years ago.