Treating compatibility as a hard constraint is easy to second-guess, but pays off in spades. Fragmentation caused by breaking hurts a lot.
-
-
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++
-
I'm not against changes in PL, but still a C# 2.0 vs a C# 5.0 does not feel the same PL
-
that's a feature not a bug. Compatible code != Compatible idioms. Stability without Stagnation.
End of conversation
New conversation -
-
-
well ... I took the TSC sources https://discuss.as3lang.org/t/the-case-when-you-dont-want-node-js/307 … it does compile and run with AVM2/AS3 :)
-
seems like it needs some changes. Do the tests pass after the changes?
-
I didn't run the tests as it was just a quick POC but I'll put that on the TODO list :)
End of conversation
New conversation -
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.