3 ms·
I have a bit of hobby experience. One of the reasons i picked haxe as a platform/language is that it's cross-platform, but easy to delve down into native, since
by chii 9y ago
I have a bit of hobby experience. One of the reasons i picked haxe as a platform/language is that it's cross-platform, but easy to delve down into native, since it's a source to source compiler. This means you write most of your code in cross-platform ways, but when shit hits the fan, you can always fight your way out by going native (which is quite seamless - such as externs, or even embedding raw native calls directly into the haxe source, useful as a last resort).
Haxe as a language, is very similar to java/c# in style (or actionscript - if you know that language). It is superficially similar to javascript too, but has a bit of semantic differences (it's not a prototypical language). The best language feature is its macro system. It is only 1 step below the LISP macro system, since macros are actual code, and you get to modify AST at compile time.
as for the library ecosystem, there's plenty of existing libraries in both pure haxe, as well as haxe externs into target native platforms. Quality vary, but you can say the same about any language's library ecosystem. Haxe's library ecosystem is mainly targeted at games - lime, openfl, haxeflixel, haxepunk, kha, babylonhx, and many many other engine/frameworks for games exist. Most of them are relatively easy to use, but as with all open source projects not backed by a large corp, there are warts, and you often have to either workaround them, or fix it (and in the process contribute!).
I haven't written any web-server/web-app using haxe, but i think it's also a popular type of app to write in haxe.
IDE integration is great with visual studio code (and intellij too).
Over all, i can't find any faults that i can't live with or fix, and am happy to continue playing with haxe. It can only improve in time.