ts2hx
ts2hx copied to clipboard
Readme does not list TS libraries tested/used against with dates. +...
I was just thinking that the Readme does not list TS libraries tested/used against, users should be encouraged to submit these with notes? By creating a list of libraries it shows feasibility and helps resolve a few objections raised against Haxe.
I was wondering if there are TS libraries currently "limited" to js target that would be worth platform generalizing, this project could maybe create stub files for more general Haxe ports or possible full transpiling. My thought is that any progress in this direction will really start to show Haxe as the better flexible solution. Imagine taking webgl TS libs and luxe-ing them, when you consider nodejs wrapper file sizes tend to be rather excessive ( node-webkit a whole browser bundled with you app, which is heavy! ), users will suddenly realize they need a Haxe solution for thier typescript project when targeting mobile.
The thing is, this tool can't really generate useful externs as of now and we need to improve it first. I've filed a few important issues which when resolved should greatly improve usability of ts2hx. Also, we're going to have Travis check that the externs are actually loadable by Haxe compiler (which is not the case currently).
After that, we'll be able to talk about using ts2hx in real world.
As for the full transpiling, I think it should be out of scope of this library and it's quite hard task we currently have no resources for. Also, I guess it should be done differently - hack into typescript compiler itself and make it output haxe instead of js, which should be much easier than trying to rewrite typescript compiler in haxe.
Am I right in thinking that typescript compiler is written in Typescript? So we should create externs for that? https://github.com/Microsoft/TypeScript