Earlier quoted context omitted.
1. While haxe has macros, they're like ocaml macros not like lisp macros. You can write a function that takes an ast and returns an ast, but because the language isn't homoiconic it feels a lot more like working with dom than like macros in lisp. 2. as2 is a superset of javascript, so it also has inline functions. 3. Having worked in haxe quite a bit, I found that the fancy type system got in the way more than it hel…
4. I have worked with haxe quite a bit and I haven't seen this; after a while you create enough libs for yourself to avoid this. Or maybe i'm missing the point here; what kind of host-specific features are you talking about? Maybe you are creating totally different software from what I am making :)
HaXe - Code Once. Deploy Everywhere.
31–40 of 62 posts
Re: HaXe - Code Once. Deploy Everywhere.
#32If they would have something that is worth being called documentation I might have actually taken this seriously.
Or the API docs?
Or maybe you rather reading a book?
http://www.amazon.com/Professional-haXe-Neko-Programmer/dp/0...
http://www.amazon.com/haXe-Beginners-Guide-Benjamin-Dasnois/...
Re: HaXe - Code Once. Deploy Everywhere.
#33Ah, "code once. deploy everywhere." Few examples of marketing to engineers spark quite the same level of skepticism as this oft-repeated claim. Ignoring, for a moment, the complexity of deploying software across multiple platforms, it's important to remember the multiple form-factor problem. The same software doesn't work from a user's standpoint on multiple platforms if the UI isn't correct for that device. The best…
Yes, you have to make allowances for the actual differences between platforms (physical buttons, screen sizes, input methods), but the rest of the code deploys extremely well across platforms. When moving between platforms, you only have to rewrite the pieces that you actually want to be different.
Re: HaXe - Code Once. Deploy Everywhere.
#34Earlier quoted context omitted.
While I disproportionally use Ruby and JavaScript on a daily basis, this statement is referring to a specific type of (common) error, which is largely alleviated by the use of static typing, and therefore not exactly untrue. I didn't take it as a disparaging of dynamic typing.
It's not untrue. But why the singling out of JavaScript? The statement is true for Python, Ruby and Lua as well. And why even mention another language or class of language in a negative way? I propose that the sentence would better have been written as > haXe has a very strict compile-time type checking feature that allows you to catch errors before testing your program in the browser It loses nothing by removing the…
As a person who likes (the good parts of) JavaScript, I read it as trying to appeal to me with promises of less debug time.
Re: HaXe - Code Once. Deploy Everywhere.
#35"multi-platform. code once. deploy everywhere." wow, that claim makes me feel old. i've lost track of how many existing/legacy ways we have to write once, deploy anywhere, multi-platform apps. it's like what they say about the great thing about universal ultimate standards: there are so many to choose from!
Re: HaXe - Code Once. Deploy Everywhere.
#36Ah, "code once. deploy everywhere." Few examples of marketing to engineers spark quite the same level of skepticism as this oft-repeated claim. Ignoring, for a moment, the complexity of deploying software across multiple platforms, it's important to remember the multiple form-factor problem. The same software doesn't work from a user's standpoint on multiple platforms if the UI isn't correct for that device. The best…
I have to say though, I've been using NME (haxenme.org), which uses the haXe language. It really does work, and it performs significantly faster than Adobe AIR or Corona.
Re: HaXe - Code Once. Deploy Everywhere.
#37Re: HaXe - Code Once. Deploy Everywhere.
#38Re: HaXe - Code Once. Deploy Everywhere.
#39Music had 7 symbols and they have perfect interoperability, Software has 2 symbols and interoperability is a dream.
Re: HaXe - Code Once. Deploy Everywhere.
#40Why is there so much skepticism in this. I am also trying to develop something like this by creating a embedded in-process web (resource) server ever where (android/iphone/wp7*/linux/win/osx), then we need to use web technology using jquery mobile with backend rpc to develop the application which should make it cross platform as well native deployed. I am developing this to simplify my clients cross platform headache…