Re:Try Haxe
by tbergeron on Sunday June 10, 2012 @09:40PM
(#4092869)
Nope.
Stop fragmenting languages, we don't need another one except if it's revolutionary.
There's some very good principles like the fact that it can compile to many languages but like CoffeeScript I just don't see the point. Want to do some c++ why not using it? Want to do some JavaScript? Then use JavaScript.
There is just too much on the table when it comes to language compilation, I mean if the compiler itself has a problem with your code? It's a bug between what you built and its runtime: what can you do about it? A client is waiting for you, you've got no time to lose contacting the compiler's developers, you're just fucked. Don't get me wrong, I like to play with these languages but that is what they are: toys.
The hard reality is that browsers only support n amount of languages and we are stuck using them.
Re:Try Haxe
by b2d on Tuesday June 12, 2012 @08:10AM
(#4100016)
This is just a bunch of unverified blanket statements and what-ifs. From my own experience, I can tell they don't apply to Haxe. Also, Haxe is revolutionary, but to understand that, you'd have to actually use it in production.
Stop fragmenting languages, we don't need another one except if it's revolutionary.
There's some very good principles like the fact that it can compile to many languages but like CoffeeScript I just don't see the point. Want to do some c++ why not using it? Want to do some JavaScript? Then use JavaScript.
There is just too much on the table when it comes to language compilation, I mean if the compiler itself has a problem with your code? It's a bug between what you built and its runtime: what can you do about it? A client is waiting for you, you've got no time to lose contacting the compiler's developers, you're just fucked. Don't get me wrong, I like to play with these languages but that is what they are: toys.
The hard reality is that browsers only support n amount of languages and we are stuck using them.