I think that it’s extremely important to understand what "Haxe, in particular(!)" sets out to be.
Haxe is a cross-platform development environment that specifically sets out to target multiple very-different environments from a single source-code file. For instance, you should expect to be able to write one program and then deploy it … natively(!) … to (say …) “Flash, HTML5, iOS, and Android.” All without changing the source-code file. (Of course, koff koff, “this is the ideal …” but Haxe usually comes dammmm close.)
The way that Haxe does this – in most, but not all, cases – is by generating source-code as output. This source-code is then fed to the platform’s native compiler, if there is one.
(But for some “targets” it simply generates the appropriate byte-code. For instance, Haxe is a much better “Flash compiler” than Adobe ever managed to produce!)
And – it actually works.
Also, it’s important to realize: from Haxe’s perspective,
Armory3D is simply "yet another package." (As are “Kha” and “Iron.”) Haxe is a general-purpose tool, which I have used for many years now in other contexts completely unrelated to computer graphics.
(“Computer graphics isn’t your day-job [yet]?”) Pay attention to Haxe, regardless! You’ll be very glad you did. (And, pay attention to Armory, too – you’re in on the ground-floor of a thing that’s soon going to be what everyone [else …] is raving about in the industry press.)