Talk:Haxe

(random heading)

(inserted for readability. ... said: Rursus (^mbork³) 11:58, 8 September 2009 (UTC))

Apparently the neutrality of this article is disputed, but the discussions page is empty thusfar. Regarding it's neutrality however, I would think the following 2 statements are suspect: "haXe is very conservative in reguards to Flash API. You can use all the Flash API like you were used to do in ActionScript." The first sentence seemingly contradicts the second sentence. "Porting code from AS2 to haXe is very easy, and you should notice additional performance when running it." This definitely needs a reference.

This sentence seems non-neutral and should have citation/explanation/be removed: "HaXe code therefore has much in common with AS3 but with many improvements and output capabilities which puts it in an entirely different category than the Adobe Compilers." Smells like original research. —Preceding unsigned comment added by 67.243.31.189 (talk) 23:08, 5 June 2010 (UTC)

Also: there are no links to the project homepage(?) or related software or documentation. Also: 'it' sounds more like an IDE capable of handling 3 types of code rather than a distinct programming language. But I could be simply reading the article wrong.

haXe is definately not an IDE, it is a programming language somewhat akin to AS or JS but with some pretty interesting generics ala STL. The (variable) typing seems pretty novel.

• This article was definitely not neutral; it sounded like a sales pitch. I have removed all the "this is the best technology evar!" style copy from the article. If additional information regarding haXe's compiler or virtual machine performance is added (particularly compared to other technologies), it should be cited from now on. Statements like "30 times faster than PHP" and "twice as fast as JVM" are dubious in the first place, and definitely require citation. Mhoskins 17:24, 18 September 2006 (UTC)

I'm trying to learn haxe and came here for resources. I noticed that this article is disputed. However I really do not understand what the concern NN-programing language does mean? Is it some kidn of Wikipedia slang? At least it doesn't open to me. If it is trying to say that haxe is not a programming language, then it is wrong. As far as I have read haxe related information, haxe seems to be a programming language that can be used to create dynamic web content, graphics and animation. Haxe code can be compiled to a browser application or to server application. A browser application is compiled to JavaScript or Flash and a server application is compiled to the web server that ships with the haxe package. The central parts of the programming language for all these three targets is the same. However not all components of the programming language are available for all targets. Tmaila 16:10, 16 October 2006 (UTC)

Looks like NN-programing language means that is allegedly "not notable" as a programming language. I beg to differ. hAxe is based on a very cool technology called Neko, seems to be a complete, well thought out and practical language, and has some unique features. I think the upside of have a Wikipedia page for it far outweighs any downside.

I am unclear as to the exact reason for the request that this entry be deleted, could the requester please clarify in this discussion, in clear and unambiguous terms, such that the request may be properly considered?

I do appreciate that some points in regard of performance may need to be qualified and or quantified (I believe independant metrics are available)

Links to the project homepage and documentation do now exist.

References to Haxe being an IDE do show that that editor had not understood the article, or that at least it was unclear to him. It is NOT an IDE btw.

any idea of a sales pitch could give the wrong impression, Haxe is open source and free as in beer. Admitedly the phrase used was "sounded like a sales pitch".

NN seems to a reference to Not Notable.

In summary it is my belief (and request) that this article should not be deleted, at least not on any grounds reported and explained thus far.

Using the same arbitrary criteria and editing, I am certain that even Jimmy Wales' few initial versions of Wikipedia itself would have been just as "not notable". Being the best qualified, perhaps we should ask him if such ground breaking works (such as HaXe) should ever again be so mindlessly labelled and thus brutalized.

It is one thing to ask for clarification but it borders on sabotage to ask to be deleted something that you do not fully comprehend. Therefore, if you would never dream of sabotaging anything that describes Jimmy Wales' creations then what in God's name would possess you to do the same to anything that Nicolas Cannasse touches ?

---

I've added an {{advert}} tag to this - as far as I know, this is justified - it looks like an ad to me. Also, someone should really rewrite this - at the moment, it's just a bunch of lists. And there don't need to be all those links at the bottom. I think that's it. Anyway, I'll take a crack at writing something just now. Even a stub would be better than what it is now! Also, would that last person (or those last people, I'm not sure) sign their post(s) please. Cam.turn 19:01, 15 November 2007 (UTC)

• OK, that looks good. Anyone want to edit it? Cam.turn 21:40, 15 November 2007 (UTC)

---

"The haXe compiler is implemented in the OCaml language. Because haXe-generated code runs on virtual machines, no knowledge of OCaml is necessary to develop applications using haXe." This seems egregious. I've never cared what any language's *compiler* is written in while developing code in that language. 69.223.58.209 (talk) 17:59, 10 November 2008 (UTC)

---

It seems a fair amount has happened since the last edits ... it now produces C++ code to a number of different targets, including iPhone, being probably the most notable. There are also examples on the net of people who are using it to develop stand-alone apps, and successfully produced iPhone apps, and given Apple's latest dev technology requirements it looks likely that using haXe to produce C++ versions from flash is the only way to legally get one's flash application on the iPhone. Seems fairly significant. It seems important also to demostrate what makes haXe different than "just another language compiler" and why that's significant - if it comes off as a salespitch that's just coincidence - I just mentioned what people are already doing it. I have no association with haXe, and I don't even use haXe myself (not yet).

The haXe website has largely removed from it's webpages it's claim about being "web-oriented", and I think rightly so ... as it can be extended to many different environments than the web when you comiple to C++, using it for standalone from desktop to mobile platforms. Adobe itself is trying to reinvent Flash as a standalone technology with Air ... but using Neko you don't even need Air, so it seems haXe is far more justified to make that claim. Frankly, as a developer I can't imagine trying to convince a client to install Air just so they could use my app, I'd use haXe instead if it came down to that. Though SWF Studio seems the best option if someone wants to develop EXE for windows from SWFs, and there are other 3rd party tools that do the same for multiple platforms, although with less favorable results.

Anyway, I don't program in haXe (not yet), I have only investigated it and although I would like to see further development in this arena (high-level multi-platform languages), especially those that allow me to thumb my nose at Steve Jobs, I tried to be objective in my edits nonetheless. Davea0511 (talk) 22:51, 19 April 2010 (UTC)—Preceding unsigned comment added by Davea0511 (talk • contribs) 22:49, 19 April 2010 (UTC)

Sample code improvement?

Right now, the example makes haXe seem to be a graphics language like POV-Ray. Unless someone feels like writing something, I'll just find a shorter snippet that makes use of type checking or class parameters. I'll try to add some comments, too. —Preceding unsigned comment added by Notostraca (talk • contribs) 00:27, 27 November 2007 (UTC)

Pronunciation

The article says :

common pronunciations are "hex" (due to the fact that the author is French), "hacks"

But in french, "haxe" is pronunced as "hacks", not "hex", so, move or remove this argument. —Preceding unsigned comment added by 81.251.245.197 (talk) 10:57, 7 August 2008 (UTC)

from the haxe site at http://haxe.org/doc/intro last edited by ncannasse "haXe (pronounced as hex) is an open source programming language." —Preceding unsigned comment added by 201.137.55.200 (talk) 04:57, 27 September 2008 (UTC)

In the french version of this same page, it is said that it is pronunced as "hax", which is pronunced as "hacks" in French. Spidermario (talk) 09:56, 2 December 2009 (UTC)

Pronunciation is a very old question, "hex" on the official web site make some people puzzled, but there is some talking in mail list could answer this : http://haxe.1354130.n2.nabble.com/How-to-pronouncing-haXe-td6434420.html and http://osflash.org/pipermail/osflash_osflash.org/2005-December/006140.html . So the answer is hex of English pronouncing /heks/ . --Icebirdyin (talk) 16:37, 5 July 2011 (UTC)

Title

Why does this show with "haxe" as the title instead of "Haxe" which it should be? -- Tom Jenkins ^(reply) 08:36, 5 November 2012 (UTC)

Fixed it. It was a tag at the top of the page. -- Tom Jenkins ^(reply) 09:07, 5 November 2012 (UTC)

Neutrality

I have edited the article removing and clarifying claims such as "full support for iPhone, Android, Windows, Unix, Mac, etc", since Haxe currently only supports a subset of the full platform API. Please do not remove this clarification. Before my edit, Haxe appeared to be a full-featured multiplatform language which it is currently not. Please do not add biased statements into the article inferring the same.

I've also wikified and improved the organization of content within the article, which was quite a mess. Please improve as necessary. -- Tom Jenkins ^(reply) 09:30, 5 November 2012 (UTC)

It's eight years later - has this changed at all? Should we look at readding them? Anyone? — Preceding unsigned comment added by 50.110.71.69 (talk) 11:09, 25 October 2020 (UTC)

Platforms

Nicolas Cannesse and friends, please stop adding the JS/NodeJS and other langs to the "full support" category unless you can prove full platform API supported. If it does, add refs to prove it. Currently the API page has 40 JS classes. Is that full support? And what about the 100 NodeJS classes? Unless you can show EVERY function from EVERY class, it does not qualify as full support and therefore Haxe cannot be used as a full replacement to that platform's native language. Saying it has full support is misleading and incorrect. -- Tom Jenkins ^(reply) 06:44, 6 February 2013 (UTC)

@Tom Jenkins

You seem to be under the impression that full support for compiling code to a certain language requires all the APIs of the respective standard library of the target language to be included into the standard library of the source language. You are mistaken.

Haxe provides support for all of JS per definition - each and every function in every prototype that JS or any third-party JS library offers, is usable from haxe directly, without any further work. The same is true for any other dynamic target language. The simple reason is that the Haxe type-system provides support for "Dynamic" instances - those can be any function, object, prototype in JS.

What you are talking about are static type definitions ("extern class" definitions in Haxe) for these APIs, but those are just a nice-to-have, not a requirement, let alone their inclusion into the standard library. In fact, by your standards, JS itself doesn't have any support for JS or any JS libraries, because there are no static type definitions in the language.

NodeJS is a third-party platform/API, and haxe usually provides support for third-party APIs in third-party libraries (in the form of collections of extern class definitions). That doesn't make the support go away.

JS is not an OOP language, but a prototyped language. There are no classes in JS. You're demanding that haxe supports things that don't even exist.

Sufficient proof for all this (where's the precedence for demanding proofs, btw?) are the both the compilers source code, and the compilers very trivially observable behavior. If you don't understand that, that's not the problem of those writing the WP article about Haxe.

So before you change the article again - please show me a single piece of JS code that in your opinion can't be written in (or used from) Haxe, and I'll give you the proof that you demand. -- TOderson

What does fully supported mean? In my opinion fully supported means: All language features from Haxe can compiled to the target platform. Also all features from the target platform could be targeted by Haxe.

Therefore I would say could say Haxe fully supports the JavaScript target. You could use the whole node.js API without writing a single line of JavaScript and do all the work in Haxe.

Also: Haxe never claimed to have a node.js target, it always said JavaScript, which is a language and not a platform. Having a API for HTML DOM in standard library is more or less just a little bit more then actually promised.-- TheHippo0 — Preceding unsigned comment added by TheHippo0 (talk • contribs) 18:48, 14 February 2013 (UTC)

Does Haxe have GADTs?

The article states that Haxe supports GADTs (generalized algebraic datatypes), by giving the examples of Option<T>, Either<T,U> and ConsList<T>. All these are merely regular ADTs (algebraic data types). The only enhancement they have over the Color type earlier in the article (properly marked as an ADT) is that they are parameterized. That alone is not sufficient to make a type a GADT: in a proper GADT, values produced by two different constructors are allowed to have different type expressions in the parameter position of their types. Just see the referenced generalized algebraic data types article. This is not a claim that Haxe does not have GADTs [I don't know; I was reading this to learn about the language]. --Noodlefarian (talk) 22:13, 15 November 2014 (UTC)

The only claim of GADTs in that language that I found was from the Haxe documentation, which also gives a regular ADT as an example. I'll remove this statement from the article. Liiiii (talk) 00:47, 7 December 2014 (UTC)

Haxe does have GADTs. I don't understand why you remove the information here just because there's no concrete example of them in the manual. How about assuming that the manual is not lying? — Preceding unsigned comment added by SimonHaxe (talk • contribs) 10:54, 7 January 2015 (UTC)

We can't assume anything contentious without a reliable source. The standard for making a claim here is Verifiability, not honesty. I think we can say the manual claims it supports GADTs; the manual itself should be evidence for that. But I don't think we can consider it a reliable source for claims like "it fully supports feature XYZ" or "it tells the truth about the language". Surely, there are other disputes here over things like that too, like JavaScript support. Again, I don't think it would be reliable for that. I have added a note at the bottom of Haxe#Enumerated types with what I think is appropriate, including a citation. Feel free to edit further. BlueGuy213 (talk) 00:08, 1 May 2015 (UTC)

Haxe/OpenFL

The following is past discussion between Wonderfl and SimonHaxe, copied here due to its relevance to the Haxe article.

You seem to be confused about the relationship of Haxe and OpenFL, so I would like to clarify. Haxe is a language and a compiler on which OpenFL is built. This relationship is directional: OpenFL depends on Haxe but in contrast Haxe has no inherent notion of what OpenFL even is. It is then irrelevant to the description of Haxe itself, which is what the introduction text should provide.

It is not the job of the Haxe wikipedia page to improve the "discoverability of OpenFL". However, as I suggested OpenFL could be listed in a "Software built on Haxe" section in the Haxe article. From a Haxe point of view it is on the same level as Flambe or Kha which could both be mentioned. — Preceding unsigned comment added by SimonHaxe (talk • contribs) 17:02, 5 February 2015 (UTC)

Look, the projects clearly are related, built by the same team, similar feature-set, and so on. Yes, I understand Haxe is a Language, but by your logic, AIR should not be mentioned on Flash Player because AIR has nothing to do with FP. True. But we mention it still because it is a close relation. I don't know what Flambe or whatever is, but if its notable, then mention it. Non notable (hardly used) stuff doesn't deserve a mention. Plus, since OpenFL is built by the same team (ie. "official") it is fine within the lead section of Haxe, while other projects may not be fine (we don't generally list third party / fandom stuff on the lead of the official article, unless its highly notable, while 1st party projects are generally listed). Wonderfl ^(reply) 04:26, 6 February 2015 (UTC)

That's just wrong information. OpenFL is built by different team; no member of the core Haxe team is directly involved with it. So your "we don't generally list third party" comment applies. You can discredit my neutrality all you want but that doesn't change the facts. — Preceding unsigned comment added by SimonHaxe (talk • contribs) 08:43, 6 February 2015 (UTC)

Book references

Hi all, I've improved the article by adding as many third-party references I could find using Google Book Search. I'm sure there are more articles/reviews on the internet but I have no time at present to add them in. The following sections have been affected:

• Lead section
• Architecture > Unified language
• Architecture > Source code

I hope all is well. If not, spend a minute to improve it!

Wonderfl ^(reply) 17:48, 6 August 2015 (UTC)

Haxe-Based Library's?

Is there any place in this page for a collection or list of library's that extend Haxe such as HaxeFlixel (http://haxeflixel.com) or HaxePunk (http://haxepunk.com)? Dancan12345 (talk) 17:56, 7 March 2016 (UTC)

External links modified

Hello fellow Wikipedians,

I have just added archive links to one external link on Haxe. Please take a moment to review my edit. You may add {{cbignore}} after the link to keep me from modifying it, if I keep adding bad data, but formatting bugs should be reported instead. Alternatively, you can add {{nobots|deny=InternetArchiveBot}} to keep me off the page altogether, but should be used as a last resort. I made the following changes:

• Attempted to fix sourcing for https://developer.palm.com/distribution/viewtopic.php?f=70&t=8499

When you have finished reviewing my changes, please set the checked parameter below to true or failed to let others know (documentation at {{Sourcecheck}}).

This message was posted before February 2018. After February 2018, "External links modified" talk page sections are no longer generated or monitored by InternetArchiveBot. No special action is required regarding these talk page notices, other than regular verification using the archive tool instructions below. Editors have permission to delete these "External links modified" talk page sections if they want to de-clutter talk pages, but see the RfC before doing mass systematic removals. This message is updated dynamically through the template {{source check}} (last update: 5 June 2024).

• If you have discovered URLs which were erroneously considered dead by the bot, you can report them with this tool.
• If you found an error with any archives or the URLs themselves, you can fix them with this tool.

Cheers.—^{cyberbot II}_{Talk to my owner:Online} 20:02, 28 March 2016 (UTC)

wwx 2016 update

Hey folks, I added the new Lua target to the list of supported platforms.

I hadn't read this article in a while, and I think it needs some love. Here's some concerns:

• " but content built with OpenFL currently suffers performance issues on mobile devices." - why are we referencing OpenFL issues here? These should all be removed.
• Performance section - this whole section looks pretty weak. I would delete it for now until we can come up with some more recent benchmarks.
• Use more specific language for features, rather than relying on comparison to other languages (e.g. explaining the "class" keyword with a comparison to Actionscript).
• "and includes experimental support for C++ and C#." - Neither of these targets are experimental anymore
• Sourcecode section - this whole section is weak as well. the links all go the same place, and it repeats the same target information we've listed elsewhere. I'd delete it and replace it with a section on editor support.

Omgjjd (talk) 09:57, 1 June 2016 (UTC)

Unexplained cleanup tag

@AtlasDuane: I don't see any content in this article that is "written like an advertisement." Why did you add this cleanup tag to the article? Jarble (talk) 03:56, 21 June 2017 (UTC)

The overall tone of the article to me is seen as promotional. For instance, you have the sentence "Major users of Haxe include BBC, Coca-Cola, Disney, Hasbro, Mattel, Nickelodeon, Prezi, TiVo, Toyota, and Zynga", this sounds like it is touting the subject as something you would want to buy, because all these well-known companies are using Haxe. Also, the phrase "The most unique aspect of the Haxe architecture" sounds to me like it is plugging Haxe with all it's unique selling points and how the product stands out from the competition, which sounds quite like what an advert would do. AtlasDuane (talk) 10:17, 22 June 2017 (UTC)

External links modified

Hello fellow Wikipedians,

I have just modified 5 external links on Haxe. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:

• Added archive https://web.archive.org/web/20070328232003/http://lists.motion-twin.com/pipermail/haxe/2007-March/007897.html to http://lists.motion-twin.com/pipermail/haxe/2007-March/007897.html
• Added archive https://web.archive.org/web/20120512000007/http://haxe.org/doc/license to http://haxe.org/doc/license
• Added archive https://web.archive.org/web/20120504021311/http://haxe.org/doc/intro to http://haxe.org/doc/intro
• Added archive https://web.archive.org/web/20120502064424/http://haxe.org/ref to http://haxe.org/ref
• Added archive https://web.archive.org/web/20120511193500/http://haxe.org/ref/enums to http://haxe.org/ref/enums

When you have finished reviewing my changes, you may follow the instructions on the template below to fix any issues with the URLs.

This message was posted before February 2018. After February 2018, "External links modified" talk page sections are no longer generated or monitored by InternetArchiveBot. No special action is required regarding these talk page notices, other than regular verification using the archive tool instructions below. Editors have permission to delete these "External links modified" talk page sections if they want to de-clutter talk pages, but see the RfC before doing mass systematic removals. This message is updated dynamically through the template {{source check}} (last update: 5 June 2024).

• If you have discovered URLs which were erroneously considered dead by the bot, you can report them with this tool.
• If you found an error with any archives or the URLs themselves, you can fix them with this tool.

Cheers.—InternetArchiveBot (Report bug) 12:34, 31 October 2017 (UTC)