-
-
Notifications
You must be signed in to change notification settings - Fork 662
Target Support Level
Haxe's multitude of targets naturally means that some targets are more actively developed, maintained, and outright useful than others. Our ecosystem has always been driven, to a large extent, by volunteers. Those tend to come and go, and we are proud that we have managed to keep the level of maintenance at a stable level over many years.
However, we have to be honest about the fact that some targets no longer receive an adequate level of attention. In order to not make these drag down the perceived quality of Haxe as a whole, we'll communicate about their situation here.
A very important point: Unless otherwise noted, all targets receive full support. We only mention targets here for which this is not currently the case.
Flash has been seen as dying and dead for a long time, and after all those years, it is time to agree. Our flash target remains very stable and usable, but is not going to receive any additional attention.
Status: Regression fixes only, new features may be supported if feasible.
Haxe and Neko have been best friends for almost two decades at this point. However, recently, its successor Hashlink has taken over Haxe's attention and while this might seem somewhat sad for Neko, we have to conclude that it's best to let sleeping cats lie.
Status: Regression fixes only, new features may be supported if feasible.
These two are always mentioned together because they were developed together and share many similarities. While the C# target does not have a proper successor (yet?), the JVM target aims to replace the Java target.
Status: Regression fixes only, new features will be supported.
Learn Haxe: Introduction | Manual | API | Try Haxe | Haxe Library Manager | Code Cookbook
Connect: GitHub | Stack Overflow | Forum | Discord | Gitter | Twitter | Facebook