3 ms·

I really wish Haxe would just take off in the application development world, it had so much potential to be what Typescript has become with the benefit of trans

• chii 5y ago
  > so much potential to be what Typescript has become the problem really is that typescript was designed to be backwards compatible with javascript - aka, valid js is valid typescript. This is a pretty big constraint. Haxe could never do this imho. It's got it's own design philosophy. I personally like haxe more, but typescript does have the advantage of the above feature, and a more robust typesystem as a result. The distinguishing feature of haxe is the macro system - which lets you generate code at compile time. It's almost as powerful as LISP, but in a familiar syntax.
• haxiomic 5y ago
  I use both haxe and typescript extensively. I yearn for what haxe could do to the js world! For example, I’m currently building a website in typescript and next.js. Next.js introduces extra tooling that generates code based on filepaths and things. It’s all very clever and complex, but this sort of thing is trivial in haxe - you just mark code to run at compile time and no extra tooling is needed. When writing haxe web projects, there’s so much less cruft: - only one system to import modules (import X) - one call to haxe.exe to compile and one output file - no strange js implicit typing (and no === operator) and so on