What the fuck am I reading? I have no idea how anyone could think this is a reasonable way to describe something and I’m a programmer.
Why not just say it’s a modern, high level, strictly typed programming language?
>What the fuck am I reading?
A pretty accurate description of what Haxe is, with bog-standard programming terms and no buzzwords.
>I have no idea how anyone could think this is a reasonable way to describe something.
Probably because they have a better grasp of what the thing they are describing is.
>Why not just say it’s a modern, high level, strictly typed programming language?
Because then you would have left out the most important parts: that it's also a cross-compiler, with a cross-platform standard library, and access to the underlying native libraries.
Again, all these are bog-standard programming terms, and all are things that Haxe offers. Furthermore, they are all core to its core mission, and the main reasons why one might choose it over any other "high level, strictly typed, programming language".
Even more so, what the fuck is difficult to parse about Haxe also being "a cross compiler"? It just means it can produce code for different platforms/environments.
Or about having a "complete cross-platform standard library"? It just means that it has a large standard library, that is portable across many platforms/environments.
Or what is difficult about it having "ways to access each platform's native capabilities"? It just means that it's not some closed sandbox system, but you can link and call into platform (e.g. iOS or .NET or whatever) APIs.
A language: It's language was originally designed to be a successor to ActionScript 3, as Haxe was originally designed to replace Flash.
A cross-compiler: The most interesting part in my opinion. Basically you can write Haxe code and target many, many different platforms. Mostly how this works is by transpiling, or translating the code into valid code in other languages.
A cross-platform standard library: This just means that it includes its standard library whenever it cross-compiles.
Ways to access native capabilities: Depending on your desired compilation target, you can use specific functionality only available on that target.
https://haxe.org/documentation/introduction/building-haxe.ht...
Because Haxe is more than that... Why would you favor less specific, less informative description over a factually correct statement?
It might be that you aren't the target audience.