|
|
|
|
|
by kigero
918 days ago
|
|
I use Haxe personally and professionally, and I love it. My use case is slightly different though, I work in R&D, so the emphasis isn't on production code but on getting a wide-ranging set of proof-of-concepts built quickly. For example, my current project required that we run the same logic in a Java service, Java client, Python client, and (coming soon) Javascript and C++ clients. Haxe worked great for getting that infrastructure up and running quickly in all of those locations so that production teams could start experimenting. I find that Haxe is great for that use case, I've got a core set of utiltiy libraries that I've been using for about a decade now that run in Java, Python, C++, and Javascript, so for a given new project I've already got a good set of code that I can use. I've also written Maven plugins - and later when I ditched Maven, Bazel rules - to incorporate Haxe projects into our build systems that work pretty well. This makes it pretty seamless to incorporate say a Haxe built Java library into a project, and the same utilities in Javascript - including debugging in Eclipse or the browser. It's not all sunshine though, I find that Haxe-compiled Python code tends to be underperformant and needs a lot of love to become as performant as, for example, the equivalent Java code. And it is true that the community is smaller, so it can be hard sometimes to get answers to questions. But it's still fun to write and work with, and I definitely see myself continuing to use it in the future. |
|