Its so positive to see a language that started as an alternative to ActionScript for making Flash games has stayed alive long after the demise of Flash. Its still used and loved because those using it have remarkable velocity.
Back in the days I've used to write libraries, generic algorithms and functions targeting ActionScript 3 (Flash) in HaXe to be able to quickly unit test them, but use them in the actual Flash projects. To unit test AS3/Flash code directly was a pain. HaXe speed up the dev workflow tremendously. Having very good memories. Now I just use modern JavaScript and TypeScript directly. But HaXe has a warm place in my heart and I am glad it still exists.
Also, the video game Dead Cells, which might even be the reason the language exists. It is an exquisitely designed and executed game which illustrates the passion of its dev team
I like Haxe, mostly, it's a nice language, built by passionate people. Typescript has replaced it in our cooperate projects, but I still love building tools in Haxe. Just to keep it fun.
I haven't touched Haxe but I still find it interesting, are there any downsides or trade-offs I should be aware off? Maybe something that bothers you that needs a workaround?
Haxe compiles to a lot of languages. Some of those language targets are better maintained than others. I've definitely had situations where some usage of esoteric Haxe features (like, deep/complex generics alongside runtime polymorphism) compiled fine to one target but compiled to invalid or incorrect code on another.
(Interestingly, in my experience the C++ target is rock solid. Though that experience is from many years ago.)
In any case, the best source for known compiler bugs is always gonna be GitHub:
Haxe makes it really easy to get started and get a feel for things, just have a go!
I found the opposite with Typescript, where it seemed like I had to already be a javascript developer to use it.
