3 ms·
The success story mentions the dev had to learn OCaml to fix bugs in Haxe, other comments here by jdk and reallyRaoul refer to inconveniences too. Elsassph ment
by benologist 12y ago
The success story mentions the dev had to learn OCaml to fix bugs in Haxe, other comments here by jdk and reallyRaoul refer to inconveniences too. Elsassph mentions some of the issues are specific to OpenFL not haxe, that's true both ways. I think you can reasonably expect to encounter issues.
Do you expect to encounter any bugs at all - outside your own code - in Java, Objective C etc when you do your native UIs?
- jonasmalaco 12y agoI don't do that many UIs at all, so I wouldn't know about that. Even so... These languages are certainly more mature than Haxe, but I do still expect to find some bugs in their standard libraries (in performance or security). And when you factor in third-party libraries, the answer is always "yes you do expect to encounter bugs" independent of the language. For me, programming is in great part reading and fixing other people's code, and I still think most of them are much more skilled than me.
- RussianCow 12y ago> Do you expect to encounter any bugs at all - outside your own code - in Java, Objective C etc when you do your native UIs? No, but I'd wager that I would spend more time re-writing the app for each native language than I would finding the inconsistencies in Haxe. (And either way, each platform has its own nuances that you have to know whether or not you use Haxe.) For the record, you'd have the same issues with solutions like Xamarin. The whole thing is a trade-off, and I have a (well-supported) hypothesis that the benefits of a (semi-)shared codebase is worth the cost of learning these nuances and inconsistencies.
- ousado 12y agoOf course you have to learn the language the compiler is implemented in when you're hacking the compiler. That's not an inconvenience, it's a tautology.