News for hackers. Stuff that matters.
Re:React/JavaScript fatigue by moonchrome on Sunday December 27, 2015 @11:09PM (#10799804)
Angular choses TS (well it's optional but so is jsx).

This is also my no.1 pain point with typescript - they focus on the typechecking part only - you want new JS features ? Use custom js transpilers, polyfills, etc. This means setting up custom typings, build system, module loader, etc.

JS land is just a huge mess to put it nicely because of th inherent problem with browser portability but its made much worse by the low barrier to entry community full of noise. I wish Dart had a better JS interop and faster compiler, in theory it solves all of my JS pains (excellent std lib, sane semantics, default package manager, modules from start, etc.) - in practice it produces big js files, compiling takes forever once you include frameworks, talking to JS is c ffi level of tedious (from what I understand they are working on improving it but its still non trivial with a significant performance overhead)

Re:React/JavaScript fatigue by SureshG on Monday December 28, 2015 @04:09AM (#10800461)
Re:React/JavaScript fatigue by moonchrome on Monday December 28, 2015 @09:52AM (#10801309)
Looking at that module : https://www.dartdocs.org/documentation/js/0.6.0/

The only documentation is bare-bones examples - 0 docs about conversion between dart<->js objects/collections/closures etc. when crossing JS interfaces. You will agree that this is an area which requires very precise description of semantics - after all we are bridging two dynamic languages with two incompatible object interfaces one on top of the other - reverse engineering the semantics sounds like a nightmare.

From here : https://github.com/dart-lang/js-interop-deprecated I was able to find this : https://docs.google.com/document/d/1X0M7iQ1PraH50353OnjKidgr... which was last updated in 2014 and I'm not sure if it's relevant.