haxe, HAXE, Haxe, HaXe or haXe?

339 views
Skip to first unread message

Joshua Granick

unread,
Jan 12, 2012, 1:44:46 PM1/12/12
to haxe...@googlegroups.com
Hi everyone!

I'm (sure) this has been discussed (at length?) before, but how do you feel about the capitalization of "haxe"

I get the impression that when the language was first created, it may have been written "Haxe", but was later changed to "haXe"?

Although this is a small detail, I think the writing of the name is (potentially) important for business reasons. It is important the name feel solid and professional, like you could reasonably write a proposal to a head CEO about your chosen language.

JavaScript is often written Javascript, which I (personally) prefer. Same with ActionScript being written as Actionscript.

A quick survey with people I know said they prefer "HaXe" over other alternatives. I find myself writing "Haxe", though (kind of?) wishing that I could write "haxe" without it being awkward. It isn't always easy when a word doesn't want to start with a capital letter.

Franco Ponticelli

unread,
Jan 12, 2012, 1:49:09 PM1/12/12
to haxe...@googlegroups.com
The official format at the time of the first book was "haXe". I personally prefer "haxe".

Franco

Cauê Waneck

unread,
Jan 12, 2012, 1:50:37 PM1/12/12
to haxe...@googlegroups.com
Yes, I like "haxe" best also :)

2012/1/12 Franco Ponticelli <franco.p...@gmail.com>

Lars Madson

unread,
Jan 12, 2012, 2:22:02 PM1/12/12
to haxe...@googlegroups.com
I use  h4*3 to keep it secret

2012/1/12 Cauê Waneck <wan...@gmail.com>

Lars Madson

unread,
Jan 12, 2012, 2:24:31 PM1/12/12
to haxe...@googlegroups.com
or just 4X3

2012/1/12 Lars Madson <rwx...@gmail.com>

Rob Fell

unread,
Jan 12, 2012, 3:24:01 PM1/12/12
to haxe...@googlegroups.com
Hi, I consider the spelling and pronounciation of any word to be inseparable.
 
If written "Haxe" or "haxe", then I'd pronounce as "Hacks" as English is my native tongue, and that's just how we swing an axe ;-)
If written "HaXe", then I'd pronounce as "HAk-Zee" as PascalCase suggests 2 words to my mind.  "Ugliest-Word-Ever" award?
If written "haXe", then I'd pronounce as "Ekz" as all emphasis is on the "X".  I've been trying to do this as I undestood that's the official spelling.
if written "hX", "hx" or "Hx", then I'd pronounce as "Hecks".
 
In my opinion, "Hecks" is a superior spoken name commercially than "Hacks" or "Ekz" (nobody knows of base-16 at sales meetings but they do know of hacking and ex-wives).  But ALL are painful to use in spoken communication / sales pitches and I'd much rather use "KungFu".  I therefore explain this upfront with a joke, and refer to haXe as "KungFu" from there on in ...
 

Juraj Kirchheim

unread,
Jan 12, 2012, 3:38:01 PM1/12/12
to haxe...@googlegroups.com
I rather like haXe, but in the end this comes down to personal taste I suppose.

However in German it helps avoiding ambiguity, because the German word
"Haxe" is short for: http://en.wikipedia.org/wiki/Schweinshaxen

Joshua Granick

unread,
Jan 12, 2012, 3:42:39 PM1/12/12
to haxe...@googlegroups.com

haXe (pronounced hex in English) is a versatile open-source high-level
multi-cultural pickled ham hock described on its website as a "universal
food".


--
Using Opera's revolutionary email client: http://www.opera.com/mail/

Joshua Granick

unread,
Jan 12, 2012, 4:26:35 PM1/12/12
to haxe...@googlegroups.com
If only it was short for Eisbaer, not Eisbein. Then we could have a cute
mascot, and even a "cult" theme song


http://en.wikipedia.org/wiki/Eisbaer


http://www.youtube.com/watch?v=S00yUmHHEv8

Joshua Granick

unread,
Jan 12, 2012, 4:28:37 PM1/12/12
to haxe...@googlegroups.com
Wow, there's even a music video for the techno mix:


http://www.youtube.com/watch?v=RXvs8IAYNXw&feature=related


On Thu, 12 Jan 2012 13:26:35 -0800, Joshua Granick

Philippe Elsass

unread,
Jan 12, 2012, 5:02:11 PM1/12/12
to haxe...@googlegroups.com

I'm all for haxe. Lowercase is the new chic.

theRemix

unread,
Jan 12, 2012, 6:22:14 PM1/12/12
to haxe...@googlegroups.com
great! i like haxe too, and i knew that the 'official spelling' was haXe. which looks great to me when it's by itself, in a sentence or something. so i just made a new haxe site (site about haxe, and written in haxe) and the uppercase X is killing me! it's so messy, especially if the word needs to be uppercased, HaXe starts to look like l33t aim speak.

here's a screenshot before i go and make the changes. lowercase haxe to be the norm from on!

 
i'll make a new thread about the site once i change all the Xs.

Tarwin Stroh-Spijer

unread,
Jan 12, 2012, 6:36:26 PM1/12/12
to haxe...@googlegroups.com
Personally I think with the capitol X it seems too geeky, a little 1337 even. On that note - we need to update the logo on the site!


Tarwin Stroh-Spijer
_______________________

Touch My Pixel
http://www.touchmypixel.com/
cell: +1 650 842 0920
_______________________


--

Joshua Granick

unread,
Jan 12, 2012, 6:38:42 PM1/12/12
to haxe...@googlegroups.com
On that note - we need to update the site! ;)

On Thu, 12 Jan 2012 15:36:26 -0800, Tarwin Stroh-Spijer
<tar...@touchmypixel.com> wrote:

> Personally I think with the capitol X it seems too geeky, a little 1337
> even. On that note - we need to update the logo on the site!
>
>
> Tarwin Stroh-Spijer
> _______________________
>
> Touch My Pixel
> http://www.touchmypixel.com/
> cell: +1 650 842 0920
> _______________________
>
>
> On Thu, Jan 12, 2012 at 3:22 PM, theRemix <jon.bo...@gmail.com> wrote:
>

>> great! i like *haxe* too, and i knew that the 'official spelling' was *
>> haXe.* which looks great to me when it's by itself, in a sentence or


>> something. so i just made a new haxe site (site about haxe, and written
>> in
>> haxe) and the uppercase X is killing me! it's so messy, especially if
>> the

>> word needs to be uppercased, *HaXe* starts to look like l33t aim speak.
>>
>> here's a screenshot before i go and make the changes. lowercase *haxe*

>> to
>> be the norm from on!
>>
>>

>> <https://lh5.googleusercontent.com/-VcxxYmrKmuc/Tw9q_VvMpJI/AAAAAAAAAC0/-wtOyv61OyU/s1600/Screen%252520shot%2525202012-01-12%252520at%2525201.17.01%252520PM.png>


>>
>> i'll make a new thread about the site once i change all the Xs.
>>
>> --
>> To post to this group haxe...@googlegroups.com
>> http://groups.google.com/group/haxelang?hl=en
>>
>

Joshua Granick

unread,
Jan 12, 2012, 6:41:41 PM1/12/12
to haxe...@googlegroups.com
So...

Perhaps it could be "haxe" when we reference it in general, but if it
seems necessary (for a blog post title, etc), perhaps we sometimes use
"Haxe"?


On Thu, 12 Jan 2012 14:02:11 -0800, Philippe Elsass
<philipp...@gmail.com> wrote:

> I'm all for haxe. Lowercase is the new chic.
> On Jan 12, 2012 10:28 PM, "Joshua Granick" <bulk...@joshuagranick.com>
> wrote:
>
>> Wow, there's even a music video for the techno mix:
>>
>>

>> http://www.youtube.com/watch?**v=RXvs8IAYNXw&feature=related<http://www.youtube.com/watch?v=RXvs8IAYNXw&feature=related>


>>
>>
>>
>>
>>
>>
>> On Thu, 12 Jan 2012 13:26:35 -0800, Joshua Granick <
>> bulk...@joshuagranick.com> wrote:
>>
>> If only it was short for Eisbaer, not Eisbein. Then we could have a
>> cute
>>> mascot, and even a "cult" theme song
>>>
>>>

>>> http://en.wikipedia.org/wiki/**Eisbaer<http://en.wikipedia.org/wiki/Eisbaer>
>>>
>>>
>>> http://www.youtube.com/watch?**v=S00yUmHHEv8<http://www.youtube.com/watch?v=S00yUmHHEv8>


>>>
>>>
>>>
>>>
>>> On Thu, 12 Jan 2012 12:42:39 -0800, Joshua Granick <
>>> bulk...@joshuagranick.com> wrote:
>>>
>>>
>>>> haXe (pronounced hex in English) is a versatile open-source high-level
>>>> multi-cultural pickled ham hock described on its website as a
>>>> "universal
>>>> food".
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> On Thu, 12 Jan 2012 12:38:01 -0800, Juraj Kirchheim <
>>>> back...@googlemail.com> wrote:
>>>>
>>>> I rather like haXe, but in the end this comes down to personal taste
>>>> I
>>>>> suppose.
>>>>>
>>>>> However in German it helps avoiding ambiguity, because the German
>>>>> word
>>>>> "Haxe" is short for:

>>>>> http://en.wikipedia.org/wiki/**Schweinshaxen<http://en.wikipedia.org/wiki/Schweinshaxen>

>>>>>> http://groups.google.com/**group/haxelang?hl=en<http://groups.google.com/group/haxelang?hl=en>


>>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>
>> --
>> Using Opera's revolutionary email client: http://www.opera.com/mail/
>>
>> --
>> To post to this group haxe...@googlegroups.com

>> http://groups.google.com/**group/haxelang?hl=en<http://groups.google.com/group/haxelang?hl=en>

Juraj Kirchheim

unread,
Jan 13, 2012, 6:25:14 AM1/13/12
to haxe...@googlegroups.com
Ok, this might be a matter of native language, but to my knowledge names are not subject to rules on letter casing (as seen here:  http://haxe.org/doc ). If "haXe" is the name, then "HaXe" is in fact incorrect casing.

In your case I would write "haXe website" and "haXe API" (because "API" is an acronym). If you do mean the domain, then I suppose haxe.org would be the way to go, since domains are case-insensitive while mixing upper and lower case characters suggests case sensitivity.

--
To post to this group haxe...@googlegroups.com

theRemix

unread,
Jan 13, 2012, 7:32:10 AM1/13/12
to haxe...@googlegroups.com
it is standardized on haxenode.org now

check

and if everyone agrees, then we can all start spelling it using a single form.

Viktor Hesselbom

unread,
Jan 13, 2012, 7:38:30 AM1/13/12
to haxe...@googlegroups.com
For what it's worth, I don't agree. I agree that it looks better with haxe or Haxe but the name is haXe and I think it's bad if a site so tightly connected to the language would essentially misspell the name.

I agree with others that both the pronunciation and the casing feels very "hackish" but I don't think we can really just essentially change the name overnight like that. It will just cause more confusion to users on the correct spelling.

viktor hesselbom



2012/1/13 theRemix <jon.bo...@gmail.com>

--

theRemix

unread,
Jan 13, 2012, 8:04:44 AM1/13/12
to haxe...@googlegroups.com
you are right, it is spelled haXe in the book and in the compiler.

i guess i'm waiting for a final word on if it will change, or not. not sure if these threads will amount to any permanent change. i can make the correct spelling work if i have to... that is, if it truly is decided by the majority that it will or will not change.

i'm not a sheep, though i will submit to the greater good of the community while throwing in my vote for 

haxe and Haxe

:)

Joshua Granick

unread,
Jan 13, 2012, 8:23:21 AM1/13/12
to haxe...@googlegroups.com
It is never too late to make a change.

...and truthfully, I spend enough time with haxelib, the command-line and
web addresses that I probably see "haxe" most often.

I think that adopting "haxe" or "Haxe" (either or both) is a fair
suggestion, that seems to be thought on favorably, if you ignore what the
book says.

Even a company as big as Apple moved from "iPhone OS" to "iOS"


On Fri, 13 Jan 2012 05:04:44 -0800, theRemix <jon.bo...@gmail.com>
wrote:

> *haxe* and *Haxe*
> *
> *
> :)

tom rhodes

unread,
Jan 13, 2012, 8:48:46 AM1/13/12
to haxe...@googlegroups.com
yeah haxe and Haxe make more sense to me too

Juraj Kirchheim

unread,
Jan 13, 2012, 10:22:38 AM1/13/12
to haxe...@googlegroups.com
On Fri, Jan 13, 2012 at 2:23 PM, Joshua Granick
<bulk...@joshuagranick.com> wrote:
> It is never too late to make a change.

True. The possibility of change doesn't imply necessity however.

> ...and truthfully, I spend enough time with haxelib, the command-line and
> web addresses that I probably see "haxe" most often.

By extension of your argument C++ should be renamed to cpp and
virtually all languages should have lower case names ;)

> I think that adopting "haxe" or "Haxe" (either or both) is a fair
> suggestion, that seems to be thought on favorably, if you ignore what the
> book says.

Assuming, that the majority of the community actually prefers "haxe",
I'm still not sure this is a good argument.
I mean, if the majority thought that haXe should be renamed to
"Ultimator Megalanguage 3000!!!!" you would see why solving this with
a poll might not be the best idea.

> Even a company as big as Apple moved from "iPhone OS" to "iOS"

That happened with the release of the iPad and was thus not a matter
of taste, but really of necessity.

Philippe Elsass

unread,
Jan 13, 2012, 10:33:55 AM1/13/12
to haxe...@googlegroups.com
Let's face it, when haxe was created it maybe wasn't too cheesy to use
mixed case to name something, but it's 2012 you know, and when I see
my blog post about haxe with all those uppercase X I really think it
sucks.

Oh and I just edited this old blog post to lowercase haxe everywhere :P

--
Philippe

Juraj Kirchheim

unread,
Jan 13, 2012, 12:08:36 PM1/13/12
to haxe...@googlegroups.com
Not that I think that a discussion of this subject would lead
anywhere, but I'll participate anyway :)

Let's face it: what is fresh/cool/hot/whatever and what isn't is
generally determined by a huge hoard of spineless drones, led by a
bunch of uncreative losers, who's biggest achievements are to rehash
the rehash of a rehash of some clever idea or interesting phenomenon
and who's authority is derived from having a great number of readers
on their blog, which is mostly about how great they are.

To be honest, I care little about this. I frankly have more important
things to do. In fact everybody does, but unfortunately many just
don't see it. These things change, mostly because those hot air
blowers need to move on, once the hoard has grazed away the new
"chic".
Personally, I find it really hard to believe, that for the first time
in human history, writing all lower case is "à la mode".

Agreed, in 2012 "haXe" might sound cheesy. So what? In 2007 Nicolas
explained his choice:
http://lists.motion-twin.com/pipermail/haxe/2007-March/007897.html
Tone is not easily conveyed, but I can only assume, the whole thing
about the "X" was a bit tongue-in-cheek back then already.

I only speak for myself, but for me, haXe is not just a random
technology, that is one of many alternatives to all the other random
technologies out there. It is a culture. It is a mental stance. It
defines it's beauty through it's pragmatism and it's importance
through it's power, and not shiny packaging and a giant stir.
I doubt the haXe community can benefit from people so shallow, that
the "cheesiness" of an "X" will make them loose their interest.

Please note, I am not saying that any choice (such as that of the
name's casing) should be intentionally made to scare people off. At
the same time I don't think any choice should be made, based on the
common definition of coolness. In 2015 "haXe" might be uncool, because
"H-A-X-E" would be. Or maybe - just maybe - people will have grown up
by then.

However, there is one thing, that has little to do with taste: history.
The name "haXe" was given to a vision, that exists since before most
of us even heard of it, let alone really believed in it. And now, that
it has reached the light, people suddenly feel uncomfortable with it's
geekishness/hackerishness, all the while THAT is the very spirit in
which the language was born and nurtured.
It never was about "trendy" or "professional" or about labels at all.
People who wanted that at the time went with Flex and what not. But
haXe was about doing the right thing. About doing something that's
exciting, not just because there's a lot of excitement, but because
it's simply vastly better than what was sold at the same time, despite
the fact, that it demands more commitment, even as a user only.

It's possible, that haXe would benefit from renaming to something that
better conveys it's power and/or elegance. Frankly, this depends on
how good the new name would be. But changing "haXe" to "haxe" or
"Haxe" means no effective improvement. It's not much unlike stripping
one of Shakespeare's plays of all its metaphors and the peculiarities
of Early Modern English, because the result is more timely.

At the end of the day, I think this choice should be made by Nicolas.
His role in all this is irreplaceable. His decisions may have a
tendency to appear quirky at first sight, but up until now, the vast
majority of them turned out great. The fact that we're all here should
be proof enough. And now PLEASE go and write some great haXe apps to
show off and spread the love!

Sorry for writing so much. But I think what I have to say on the
subject is now exhausted :)

Joshua Granick

unread,
Jan 13, 2012, 1:44:20 PM1/13/12
to haxe...@googlegroups.com
I absolutely agree that a small poll on a forum can't presume to decide
everything. Of course Nicolas' opinion on this matters!

Haxe still has an 'x' inside ;)

Even Ajax, that Nicolas mentioned six years ago, is written today as
"Ajax" and not "AJAX" as it was in the past (as it has kind of grown to
represent asynchronous transfers in Javascript, not just XML)

Ajax still has an 'x' inside :)

> However, there is one thing, that has little to do with taste: history..

Nicolas Cannasse

unread,
Jan 13, 2012, 2:58:32 PM1/13/12
to haxe...@googlegroups.com
I'm currently on vacations, so can't answer all the mails, but here's my
take :

the official way of writing the language is haXe, with an uppercased X.
It feels maybe a bit geeky but I kindof like it this way. Also someone
told that it makes it spell in english as "hecks" (or "hex" ?) instead
of "hacks" which is good as well.

As for haXe-related technologies, I don't think they need to keep the
uppercase X, so for instance haxenode is fine for me, it doesn't need to
be haXenode since it's a different word.

Best,
Nicolas

theRemix

unread,
Jan 13, 2012, 4:10:44 PM1/13/12
to haxe...@googlegroups.com
i like the idea of having haxejs haxenode HaxePokemon be spelled with freedom of choice, where i will always refer to the core, original language and compiler as haXe to keep mindful of the origins. i like how the proper case when it's by itself.

haXe

i'd like to see the new haxe.org site use the proper case to promote and remove confusion.

thanks Nicolas! enjoy your much deserved vacation!

Tony Polinelli

unread,
Mar 7, 2012, 3:18:59 PM3/7/12
to haxe...@googlegroups.com
Okay, i missed Nicolas' reply, and feel this thread needs to continue - for our little marketing week. 

writing haXe IS geeky, and unpopular (as this thread prooves) so why does it remain. Just because Nicolas' has a slight liking for it. With the overwhelming opinions otherwise, i think it should be best to change it. I often support the iron fist of Nicolas to avoid semantic little battles, but if haxe IS opensource, the opinions of, especially the core (Caue, Franco) should matter. These opinions exist for good reason (as explained in this thread) and shouldnt just be dismissed. As i recall this isnt even the first time the matter has come up. 

So people who support 'haxe' over 'haXe' (in this thread) :

Joshua Granick 

Franco Ponticelli

Cauê Waneck

Philippe Elsass

theRemix

tom rhodes
 
Tarwin Stroh-Spijer

Tony Polinelli


people who support haXe:

Juraj Kirchheim

Nicolas Cannasse


If the only reason for it to remain as haXe is because Nicolas 'kindof likes it this way', i think thats a bit poor. 

>> Also someone told that it makes it spell in english as "hecks" (or "hex" ?) instead of "hacks" which is good as well.

this is rediculous - the (mis)pronunciation of the language is another matter, but definitely not a reason to (mis)spEll it. 






--



--
Tony Polinelli
http://touchmypixel.com

Tony Polinelli

unread,
Mar 7, 2012, 3:22:29 PM3/7/12
to haxe...@googlegroups.com
having that said, getting 8 people on a thread ISN'T a soul reason to change things, but i think it is reflects the wider view of the community - and definitely should just be dismissed 

JLM

unread,
Mar 7, 2012, 3:54:16 PM3/7/12
to haxe...@googlegroups.com
I prefer   haXe   since memorably marketing supports adjusting a word to be memorable either by misspelling it in a cool way or with some other trick.  HaXe and haXe having a capital X make it more interesting and more memorable, even if it annoys some that could actually considered good since it is better to remember a product because a name jars you rather than forget it as being samely and unmemoriable.  I really suspect a marketing company would keep the capital X it's already part of haXe character and branding.

sorry ( not corrected spelling above, browser keeps jumping out when I try to right click on the misspelt words. )

I think largely these discussions are not going anywhere the new site is a good step forward it is the overall look that is important and the ability to use and see haXe in use.  The new site will take awhile to impact, the exact catch phase will probably make no real impact, unless we go with the 'one language' in which case it may be controversal enough to get more twitter coverage.

The new logo and the site is good, but these other side issues being discussed are not really so important, but I think it is important to retain the haXe identity as it's name builds presence, familarity and reputation, a slow process where too much rebranding could ruin.

Axel Huizinga

unread,
Mar 7, 2012, 3:58:51 PM3/7/12
to haxe...@googlegroups.com
Am 07.03.2012 21:18, schrieb Tony Polinelli:
Okay, i missed Nicolas' reply, and feel this thread needs to continue - for our little marketing week. 

writing haXe IS geeky, and unpopular (as this thread prooves) so why does it remain. Just because Nicolas' has a slight liking for it. With the overwhelming opinions otherwise, i think it should be best to change it. I often support the iron fist of Nicolas to avoid semantic little battles, but if haxe IS opensource, the opinions of, especially the core (Caue, Franco) should matter. These opinions exist for good reason (as explained in this thread) and shouldnt just be dismissed. As i recall this isnt even the first time the matter has come up. 

So people who support 'haxe' over 'haXe' (in this thread) :

Joshua Granick 

Franco Ponticelli

Cauê Waneck

Philippe Elsass

theRemix

tom rhodes
 
Tarwin Stroh-Spijer

Tony Polinelli

I also prefer haxe most simply because it's easier to type and was a litte sad to see the new logo with HAXE
instead of
Anyway both show that Nicolas doesn't seem to care too much about the way it is spelled.

Philippe Elsass

unread,
Mar 7, 2012, 4:09:42 PM3/7/12
to haxe...@googlegroups.com
Joshua, theRemix (haxenode) and I have started using lowercase haxe in all our materials (websites, blogs) so hopefully we'll quietly push this casing change :P
Philippe
fhjcifeg.png

Lars Madson

unread,
Mar 7, 2012, 4:11:23 PM3/7/12
to haxe...@googlegroups.com
I prefer haXe too, more fun.

2012/3/7 Axel Huizinga <ax...@go2ghana.de>
fhjcifeg.png

Tarwin Stroh-Spijer

unread,
Mar 7, 2012, 4:15:11 PM3/7/12
to haxe...@googlegroups.com
My only real problem with "haXe" is it's geeky nature. When I see it always just seems I'm reading '1337'.



Tarwin Stroh-Spijer
_______________________

Touch My Pixel
http://www.touchmypixel.com/
cell: +1 650 842 0920
_______________________


fhjcifeg.png

Mark Ford

unread,
Mar 8, 2012, 12:23:07 AM3/8/12
to haxe...@googlegroups.com
I will say this both ways...

On the one hand this is Nicolas's baby so if he wants to call it haXe - however misguided that is - then I guess it's his prerogative.

But then again, it seems to me the community is both passionate and divided over these issues and, as pointed out earlier, it may well become haxe by default.  For me, in my future posts, I am tempted to simply refer to it as Hex or Hx and you will all know what I am saying. :-p

I think if we really want this issue sorted then it's probably best we create a small independent focus group whose members are best qualified with real life expertise in the areas of branding and marketing.  Any nominations?

Nicolas Cannasse

unread,
Mar 8, 2012, 7:18:00 AM3/8/12
to haxe...@googlegroups.com
Le 07/03/2012 21:18, Tony Polinelli a �crit :

> Okay, i missed Nicolas' reply, and feel this thread needs to continue -
> for our little marketing week.
>
> writing haXe IS geeky, and unpopular (as this thread prooves) so why
> does it remain. Just because Nicolas' has a slight liking for it. With
> the overwhelming opinions otherwise, i think it should be best to change
> it. I often support the iron fist of Nicolas to avoid semantic little
> battles, but if haxe IS opensource, the opinions of, especially the core
> (Caue, Franco) should matter. These opinions exist for good reason (as
> explained in this thread) and shouldnt just be dismissed. As i recall
> this isnt even the first time the matter has come up.

I'm really open to discussions in general, but honestly I don't think
that either changing the spelling or writing of haXe will do much change
in terms of its popularity.

Or at lease, if you think about the top 5 things that could increase
haXe popularity, their not part of it.

I have no personal issue if people write it Haxe or haxe or even HAXE
(the new logo use capitals for instance), so what about being agnostic
here ?

Actually, I would prefer that the community focus on more important
contributions such as improving the website, the documentation, the
tools, etc.

I can understand that such topics are popular because everybody can give
its own opinion without to do any actual work but in the end I think
that people involvement and actual time spent doing real things will
make the difference.

Best,
Nicolas

Tony Polinelli

unread,
Mar 8, 2012, 7:52:10 AM3/8/12
to haxe...@googlegroups.com

>> actual time spent doing real things will make the difference.

The quality of haxe is not in doubt to anybody. It has been stated many times that its value far surpasses the popularity of the language. This is why people have been interested in looking at ways to make it more marketable, and friendly to the wider community, and trusted commercially. The casing of the X has come up a number of times, and people have stated that it may be a hinderance when first showing the language to people (look at the humor in the other thread - ninjas). 

Technical work is great - and makes a language, but marketing it is important too, but unfortunately that revolves around discussion and opinion, which i dare say doesn't fall into the category of not 'doing actual work' - otherwise advertising agencies wouldn't exist. As you said, this is a small topic - there are much bigger fish to fry, but since it *has* come up many times, maybe it should be addressed. 

so where should we go from here? staying the same or changing



On Thu, Mar 8, 2012 at 11:18 PM, Nicolas Cannasse <ncan...@motion-twin.com> wrote:

Gary Bernstein

unread,
Sep 27, 2014, 6:59:16 AM9/27/14
to haxe...@googlegroups.com
Shouldn't it be haxi, with an "i", if it stands for "has an x inside"? :)

Was the "haxi" domain simply taken, or why isn't it haxi?

On Thursday, January 12, 2012 8:44:46 PM UTC+2, Joshua Granick wrote:
Hi everyone!

I'm (sure) this has been discussed (at length?) before, but how do you feel about the capitalization of "haxe"

I get the impression that when the language was first created, it may have been written "Haxe", but was later changed to "haXe"?

Although this is a small detail, I think the writing of the name is (potentially) important for business reasons. It is important the name feel solid and professional, like you could reasonably write a proposal to a head CEO about your chosen language.

JavaScript is often written Javascript, which I (personally) prefer. Same with ActionScript being written as Actionscript.

A quick survey with people I know said they prefer "HaXe" over other alternatives. I find myself writing "Haxe", though (kind of?) wishing that I could write "haxe" without it being awkward. It isn't always easy when a word doesn't want to start with a capital letter.

Cambiata

unread,
Sep 27, 2014, 12:21:45 PM9/27/14
to haxe...@googlegroups.com

Was the "haxi" domain simply taken, or why isn't it haxi?
 
Wild guess: By the same reason as you don't spell your name "Gari"... :-)

Gary Bernstein

unread,
Sep 27, 2014, 2:55:53 PM9/27/14
to haxe...@googlegroups.com
Oh, I thought it's cuz they didn't want haxe to sound like a "taxi" :)

"I write in haxi" sounds and looks too much like "I ride in taxi"

On Sat, Sep 27, 2014 at 7:21 PM, Cambiata <jona...@gmail.com> wrote:

Was the "haxi" domain simply taken, or why isn't it haxi?
 
Wild guess: By the same reason as you don't spell your name "Gari"... :-)

--
---
You received this message because you are subscribed to a topic in the Google Groups "Haxe" group.
For more options, visit https://groups.google.com/d/optout.

j...@justinfront.net

unread,
Sep 27, 2014, 6:44:05 PM9/27/14
to haxe...@googlegroups.com
Gary

Haxe is not something that was just created yesterday it has spent many
years evolving, in a rich opensource community of creative developers,
so your suggestions seem quite flippant. Did you read the History? Haxe
is not as you imagine an English play on words, but rather a french
creation, so the 'e' is silent, like a deadly ninja, so it would be
impossible to remove it now.

http://haxe.org/manual/introduction-haxe-history.html

Best Justin


On 27/09/2014 19:55, Gary Bernstein wrote:
> Oh, I thought it's cuz they didn't want haxe to sound like a "taxi" :)
>
> "I write in haxi" sounds and looks too much like "I ride in taxi"
>
> On Sat, Sep 27, 2014 at 7:21 PM, Cambiata <jona...@gmail.com
> <mailto:jona...@gmail.com>> wrote:
>
>
> Was the "haxi" domain simply taken, or why isn't it haxi?
>
> Wild guess: By the same reason as you don't spell your name
> "Gari"... :-)
>
> --
> To post to this group haxe...@googlegroups.com
> <mailto:haxe...@googlegroups.com>
> http://groups.google.com/group/haxelang?hl=en
> ---
> You received this message because you are subscribed to a topic in
> the Google Groups "Haxe" group.
> For more options, visit https://groups.google.com/d/optout.
>
>
> --
> To post to this group haxe...@googlegroups.com
> http://groups.google.com/group/haxelang?hl=en
> ---
> You received this message because you are subscribed to the Google

Gary Bernstein

unread,
Sep 27, 2014, 7:07:43 PM9/27/14
to haxelang
Ah, that makes sense now. Sorry about that. I just got here and read something about that acronym and thought it was amusing, but I should have read history first. The silent 'e' is a nice touch. Thanks for explaining that. Haxe looks amazing and I'm very happy to have found it.

On Sun, Sep 28, 2014 at 1:42 AM, j...@justinfront.net <j...@justinfront.net> wrote:
Gary

Haxe is not something that was just created yesterday it has spent many years evolving, in a rich opensource community of creative developers, so your suggestions seem quite flippant.  Did you read the History? Haxe is not as you imagine an English play on words, but rather a french creation, so the 'e' is silent, like a deadly ninja, so it would be impossible to remove it now.

http://haxe.org/manual/introduction-haxe-history.html

Best Justin


On 27/09/2014 19:55, Gary Bernstein wrote:
Oh, I thought it's cuz they didn't want haxe to sound like a "taxi" :)

"I write in haxi" sounds and looks too much like "I ride in taxi"

On Sat, Sep 27, 2014 at 7:21 PM, Cambiata <jona...@gmail.com
<mailto:jona...@gmail.com>> wrote:


        Was the "haxi" domain simply taken, or why isn't it haxi?

    Wild guess: By the same reason as you don't spell your name
    "Gari"... :-)

    --
    To post to this group haxe...@googlegroups.com

    http://groups.google.com/group/haxelang?hl=en
    ---
    You received this message because you are subscribed to a topic in
    the Google Groups "Haxe" group.
    For more options, visit https://groups.google.com/d/optout.


--
To post to this group haxe...@googlegroups.com
http://groups.google.com/group/haxelang?hl=en
---
You received this message because you are subscribed to the Google
Groups "Haxe" group.
For more options, visit https://groups.google.com/d/optout.

Todor Angelov

unread,
Sep 28, 2014, 4:31:02 AM9/28/14
to haxe...@googlegroups.com
1. HX 
2. HAXE
3. haxe
:)

Tarwin Stroh-Spijer

unread,
Sep 28, 2014, 10:11:29 PM9/28/14
to haxe...@googlegroups.com

0. Haxe

--

Benjamin Dubois

unread,
Sep 30, 2014, 12:32:01 AM9/30/14
to haxe...@googlegroups.com
2 years archeology. This topic is close now since Haxe has lost its uppercase X.

To answer your question : Haxe doesn't mean "Has An X inside". AFAIK "has an X inside" is a assert from Nicolas that "justify the presence of an x in Haxe, cause everybody know that when something is spelled with an x inside.It's always successful. See Faxbook, twixter, javaxcript... and so on


--
Reply all
Reply to author
Forward
0 new messages