The documentation looks absolutely horrible. I can find in many ways how it can compile to multiple targets, but no easy way to find out how it actually looks like. Any "hello world" example that does not contain language reference? Maybe "a gentle introduction to haxe" before "compiler metadata"?
http://haxe.org/doc/snip http://haxe.org/doc/snip/hello
Haxe 2.10 - Now with Java and C# targets
41–44 of 44 posts
Re: Haxe 2.10 - Now with Java and C# targets
#42Earlier quoted context omitted.
> Adding the additional translation layer increases the potential of bugs > the implementation has information that could be used to generate better bytecode These are theoreticals. Let me analogize. Some algorithms have a worst-case big O that is significantly worse than the average case. So even though the algorithm could have very poor performance in certain situations, it's better for the "real-world" cases that…
> we gain more than we lose What do you gain? As far as I can tell, there is only loss. > the need for flexibility that drives Haxe, and you aren't gaining additional flexibility from bytecode. Exactly what flexibility does this provide?
Re: Haxe 2.10 - Now with Java and C# targets
#43Haxe is interesting only because of its targets. No advanced type features at all.
What sort of advanced features are you hoping for? Genuinely interested, I use Haxe and find it's type system advanced enough for me - but maybe there's awesome features in other languages that I don't know about yet.
User should read up on Haxe and may well leave attribution of novelty to correct adjectivation, reads less pedantic in many ways.
Re: Haxe 2.10 - Now with Java and C# targets
#44Cross-platform tools often have a single user interface that tends to look foreign on every platform (sencha touch), or they force you to code a different ui for every targeted platform (titanium?). How is the ui problem is usually tackled with haxe? I tried googling a bit, but didn't come up with a conclusive answer.
The new java target and already available JNI usage targets Android.
There is also http://lib.haxe.org/p/hxffi and a established way to call iOs framework code with hxcpp, which is through the CFFI . You should probably have a read (mostly for Cauê Waneck's posts): https://groups.google.com/forum/#!topic/haxelang/9_FHI5cDue0