I fear that the growing support for half-baked type systems in JS will set back good type systems for another decade (like Java)
@markijbema afaict Angular 2.0 requires type syntax, so I wouldn't be so sure.
-
-
@wycats@markijbema is that true? You're supposed to be able to write (mildly convoluted) ES5 Angular apps. -
@theefer@markijbema http://note.io/1u8IYOU feels too convoluted to be practical. Regardless, types mandatory even when convoluted ES5. -
@wycats some have suggested libraries to abstract the boilerplate (say w syntax sitar to Angular 1.x). We'll see how that looks -
@theefer Surprised the Angular team isn't abstracting it. Maybe they don't expect much desire for non-AtScript usage? -
@wycats Or the assumption may be that if it's possible and desired, it will happen anyway? All seems rather early days anyway.
End of conversation
New conversation -
-
-
@wycats@markijbema type syntax is not a requirement. Angular 2.0 apps can be developed in ES5, or CoffeeScript or whatever. -
@benlesh Type syntax, no, but types yes. Types power the DI in Angular 2.0.@markijbema -
@wycats@markijbema I'm sure@vojtajina can explain it in better detail. But the types are transpiled into metadata/annotations. -
@BenLesh@wycats@markijbema DI needs annotations, does not have to be type. Annotations can be easily expressed in ES5.
End of conversation
New conversation -
-
-
@wycats@markijbema this is not true! It is up to you!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.