[johnhattan]

HaxeDevelop is a rebranded version of FlashDevelop. While it's built in .NET, apparently enough of it was built with Windows-only code that porting wasn't in the cards.

HaxeDevelop's best (IMHO) feature was that it could switch targets easily and integrated seamlessly with the Flash runtime's debugger. So you could build and debug quickly using the Flash runtime and then compile your project to native code for production.

But yeah, in a perfect world VSCode integration would be the way to go forward.

[jdonaldson]

The Haxe community is made up of a lot of folks interested in general cross-platform dev, but there's also a ton of folks from the Flash diaspora. Accordingly, many tools and frameworks are evolutions of the "Flash way" (HaxeDevelop, OpenFL), while other tools and frameworks are starting from scratch, or adapting to other ecosystems (vscode-haxe, Kha).

There's always been calls to "unify" the frameworks, tooling, etc., but I don't think that's a healthy environment for Haxe. Haxe exists as a way to avoid ecosystem lock-in. It's a bit antithetical if the community imposed restrictions on how to develop with Haxe.

[camus2]

HaxeDevelop isn't going to run on Linux or Mac, that's the point. Programming communities should focus on writing language servers and let developers use their favorite IDE instead of forcing people to use a specific IDE.

[markknol]

There is a language server build by the Haxe team. https://github.com/vshaxe/haxe-languageserver HaxeDevelop consumes that.

If you want a cross-OS IDE, or something that works on mac/linux, then use vscode + vshaxe.