ncannasse

Haxe is not dynamically typed, it can compile to dynamically typed platforms, but it can also compile to statically typed platforms while remaining statically typed.

For switch it uses Hashlink/C code generation so it's native C that is compiled on the console.

That would surely help if you could tell us what Haxe specific problems you had.

Hi ben, it's clearly not the best place to discuss this, but I still wanted to leave you some message here, hope it'll reach you.

I don't think that you get a good language by having design by committee. I'm all for democratic process and contributions in many different areas, but you simply can't apply that to language design, but you really need a way to understand and see the big picture, and not only reason about a particular local feature.

The only thing we could do better here would be to spend more time motivating my decisions so they seem less random to people from outside, but it's time consuming to do so and I'm sadly lacking the time for it.

I understand how this can be badly perceived but you shouldn't put ill intend behind what has happened to your proposals.

Also, I saw you started designing your own language, which is very different from Haxe from what I have seen, so it seems to me what you wanted Haxe to be was simply not what it is and will be.