Live data from Hacker News

HaXe - Code Once. Deploy Everywhere.

haxe.org

31–40 of 62 posts

Re: HaXe - Code Once. Deploy Everywhere.

#31

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 :)

Networking, drawing to the screen, video and audio, click events, etc. I think that's most of what most apps are doing. If you're doing something numeric (like a simulation or a computer algebra system) my previous statement doesn't apply.

Re: HaXe - Code Once. Deploy Everywhere.

#32
post #7

If they would have something that is worth being called documentation I might have actually taken this seriously.

Like the gigantic wiki?

http://haxe.org/doc

Or the API docs?

http://haxe.org/api

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.

#33

Ah, "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…

http://unity3d.com/

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.

#34
post #27

Earlier 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…

My guess is that rather than give an exhaustive list, the author wanted to give an example of a familiar language _without_ static typing. As Haxe is more similar to ECMAScript than Python, Ruby, Lua etc. - it's the most appropriate comparison.

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!

Indeed, this was the promise of C, and it was largely realized: there are C compilers for almost every platform. (You can even use Emscripten to "compile" C to JavaScript, but don't expect miracles.)

Re: HaXe - Code Once. Deploy Everywhere.

#36

Ah, "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…

Right -- I understand this is the type of phrase that's used a lot, but doesn't really follow through.

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.

#38
The Stormpulse map was originally written in AS2 by yours truly. We recently moved it over to haXe and are now generating a .swf and an iOS app from the same codebase. I should say by "we moved it over" I mean an MIT Media Lab PhD. No way could I have figured out how to manage haXe/NME/X Code the way he did to pull it off. But it does work. The biggest work left is to make the iOS app feel like a proper iOS app rather than the Flash app on an iPad.

Re: HaXe - Code Once. Deploy Everywhere.

#39
Why 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. Sometimes i wonder why there is no product in the market which can do this, which will make my life easier.

Music had 7 symbols and they have perfect interoperability, Software has 2 symbols and interoperability is a dream.

Re: HaXe - Code Once. Deploy Everywhere.

#40
post #39

Why 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…

Software has two symbols? I'm not sure what the analogy is, but the best I can think of would be either opcodes or functions, and pretty much everybody has a lot more than two.
Post reply on HN