Live data from Hacker News

Think twice before naming your new programming language

guillaume-nargeot.blogspot.com

11–17 of 17 posts

Re: Think twice before naming your new programming language

#11

I think this goes for a lot more than just programming languages. FOSS projects in general tend to pick some generic English words as names that make them really hard to find. I've even seen a few startups that've fallen into this pit. Ironically, the fact that most "decent" domain names have been taken is forcing startups to put more time into coming up with a name which could ultimately help their searchability, th…

FOSS projects in general tend to pick some generic English words as names that make them really hard to find

This is related to most F/OSS projects having a crushing deficit in the marketing skills department. Notice how most don't have a visual identity, either? And how they typically launch mostly undocumented, on somebody else's website?

I had a checklist for launching A/Bingo, and held off on it for a week past when the code was ready, because the marketing wasn't. Logo, slogan, landing page, usage documentation, install documentation, live demo, domain name. It practically killed me because I was/am proud of that project and wanted to start collecting feedback but I know it won't spread if I don't do a proper job of it.

There is no point in spending dozens or hundreds of engineer hours on a project if it languishes in obscurity because you were too disinterested to, e.g., put a logo on it. (Mine cost $210. Cheap at the price!)

Incidentally, even if you can't get the exact match domain .com domain name for your project, for OSS everyone is just going to Google you anyhow. Name the project well and you will rank for your own name very, very fast as a consequence of your normal marketing activities, since good OSS tends to collect authoritative links with laser focused anchor text.

Re: Think twice before naming your new programming language

#12
These two searches seem to work: Factor programming language R programming language

So instead of writing "Factor tutorial" (for which btw Google asks you if you mean the language), write "Factor programming language tutorial". Being more specific about what you're looking for helps.

Re: Think twice before naming your new programming language

#13
eg of what I think of a badly named language.* I think * clojure is a sorry name for the fascinating language it is.

In the words of Rich Hickey - It's a ploy on closures and is supposed to be pronounced as cloSSure (and the domain was available; fulfilled his requirements of combining c for clr, j for java). Many have been spelling it as cloJure, even stuart halloway(author of the only book available on clojure) has couple of podcasts with cloJure pronounced with the emphasis on J.

my little rant aside, the name(in context to the article) is instant seo juice. input just one word and google spits everything clojure, no distractions from random links.

I have taken a mid way to pronounce clojure - clozure.

Re: Think twice before naming your new programming language

#15
What about Ruby? Python? Java? Those are pretty "normal" terms. The only reason search engines can come up with nice results for those languages is that there are thousands of pages out there which mention the word "python" or "ruby" or "java" in context of programming.

I agree that J and R are (and will be) very hard to search for, but not Factor. If/when the language becomes popular, a Google search for "factor" will be dominated by results that relate to the programming language.

Re: Think twice before naming your new programming language

#16

What about Ruby? Python? Java? Those are pretty "normal" terms. The only reason search engines can come up with nice results for those languages is that there are thousands of pages out there which mention the word "python" or "ruby" or "java" in context of programming. I agree that J and R are (and will be) very hard to search for, but not Factor. If/when the language becomes popular, a Google search for "factor" wi…

I remember the first time I went searching for the Io and Processing languages, expecting that the generality of the names would make it hard. I got good results right away.

On the other hand, some names make it hard to talk about things. For example, much as I like the Sequel ORM for Ruby, having a aural discussion about it is more trouble than it should be because you have to be clear when you are talking about the RUby library or SQL. (Pedant alert: SQL should be pronounced ess que el anyway, but few people do.)

Post reply on HN