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.
--
To post to this group haxe...@googlegroups.com
http://groups.google.com/group/haxelang?hl=en
However in German it helps avoiding ambiguity, because the German word
"Haxe" is short for: http://en.wikipedia.org/wiki/Schweinshaxen
--
Using Opera's revolutionary email client: http://www.opera.com/mail/
http://en.wikipedia.org/wiki/Eisbaer
http://www.youtube.com/watch?v=S00yUmHHEv8
http://www.youtube.com/watch?v=RXvs8IAYNXw&feature=related
On Thu, 12 Jan 2012 13:26:35 -0800, Joshua Granick
I'm all for haxe. Lowercase is the new chic.
--
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!
>>
>>
>>
>> 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
>>
>
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>
--
To post to this group haxe...@googlegroups.com
--
...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*
> *
> *
> :)
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.
Oh and I just edited this old blog post to lowercase haxe everywhere :P
> --
> To post to this group haxe...@googlegroups.com
> http://groups.google.com/group/haxelang?hl=en
--
Philippe
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 :)
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..
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
--
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 rhodesTarwin Stroh-Spijer
Tony Polinelli

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
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.
Was the "haxi" domain simply taken, or why isn't it haxi?
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.
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:haxelang@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.
0. Haxe
--
--