The idea is that yes, you do 99.9% of your work in Haxe and it is robust enough to handle things. Only times you might drop down to your native compiled languag

The idea is that yes, you do 99.9% of your work in Haxe and it is robust enough to handle things. Only times you might drop down to your native compiled language is if you want to interface with a native library/component for which there is no 3rd party extension to Haxe yet. Even then there are Haxe based methods to fit most of those cases too. I think the analogy is accurate: Haxe is not meant to be used to compile to native and then modified in native further. It can be... but the general usecase is to write everything in Haxe and not have to then modify the transpiled result. Similar to typescript in a way... you can add JavaScript after the fact, but most likely you’d directly add native untyped JavaScript within your Typescript code, not directly to your transpiled result.