Treating compatibility as a hard constraint is easy to second-guess, but pays off in spades. Fragmentation caused by breaking hurts a lot.
I thought @Gankro was referring to deeper divergence of AS3 from ES3 than AS2 :)
-
-
ah oki, well ... AS3 is fully compatible with ES3, see the spechttps://github.com/as3lang/ActionScript3/wiki/Specification#2 …
-
@github that says AS3 was compatible with ES4, which failed for the same reason. -
ES4 wasn't remotely compatible with ES3 in the real world.
-
imho the fail/rejection of ES4 was more a timing issue of "we are not ready for that yet" at the time
-
as an avid user for TS and champion of decorators in TC39, I don't agree
-
adding features forever to a PL can be problematic, eg. the perl6/php6/python3 problem
-
those are examples of incompatible changes not "adding features forever"
-
examples of compatible changes: JS, WWW, Ruby, Java, C#, C++
- 2 more replies
New conversation -
-
-
so in 2006 something like ES4/AS3 was breaking the web, but 10 years later TS/ES6 does not ... politics :P
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
now yeah TC39 argued about ES4 (AS3), canceled it and now few years after we have things like TypeScript
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.