News for hackers. Stuff that matters.
Re:What will happen when we run out of names for JavaScript ... by maga on Saturday May 06, 2017 @04:52PM (#14282195)
That's easy - use non-English names. I, for one, try to give Latin names where possible. I'm currently working on a SPA called "scriptare"[1] (which is Latin for "write"). The front-end part is called "calamus" (pencil) and the node.js back-end is "praeceptor" (teacher), and the ML back-end is "augur" (seer).

As luck would have it, I was just putting out a new version of our in-house MVC framework called "Compago"[2] (structure/framework in Latin). While it has been used in various versions since 2013, we didn't share it until 2015, and even then didn't document beyond the JSDoc comments since we are not interested in popularizing it.

[1]http://scriptare.com (in closed beta)

[2]https://github.com/scriptare/compago

Re:What will happen when we run out of names for JavaScript ... by Yetanfou on Saturday May 06, 2017 @05:57PM (#14282479)
Swahili is a great language for finding good-sounding project names. Most words are easily pronounceable with a 'pleasant' balance between vowels and consonants, they just 'sound good'.

Take a word like 'rafiki', Swahili for 'friend'. That's a perfect name for some social platform. Or 'nena' - which means 'speak' - for a chat app. Just get a Swahili-whatever dictionary and you'll soon have more project names than you can shake a fimbo at. Fimbo is Swahili for 'stick', by the way.

Re:What will happen when we run out of names for JavaScript ... by marak830 on Saturday May 06, 2017 @08:50PM (#14283210)
Oh I like that idea, and I'm looking to rebrand the software I have been working on and off for 2+ years, I will have to look up some translations online.

Thanks!

Also makes me wonder about some other languages too.

Re:What will happen when we run out of names for JavaScript ... by zerocrates on Saturday May 06, 2017 @06:35PM (#14282625)
"Rafiki" might bring up some problematic associations with Disney.
Re:What will happen when we run out of names for JavaScript ... by DonaldFisk on Saturday May 06, 2017 @07:40PM (#14282932)
"Scribere" is Latin for "to write". It's third conjugation, not first (-are). "Calamus" is Latin for "reed" but it can also mean "pen": https://en.wikipedia.org/wiki/Kalamos . Pencils weren't invented until the 16th century. The modern Latin word for pencil is "plumbum" (lead): https://glosbe.com/la/en/calamus

Fun fact: the word "pencil" is related to the word "penis". See http://www.etymonline.com/index.php?term=pencil

Re:What will happen when we run out of names for JavaScript ... by maga on Sunday May 07, 2017 @12:02AM (#14283779)
"Scriptare" too if this[1] to be believed, though not in classical times though. And yes, I mixed up pen and pencil there.

[1] http://latin-dictionary.net/definition/34351/scripto-scripta...

Re:What will happen when we run out of names for JavaScript ... by Turing_Machine on Saturday May 06, 2017 @08:21PM (#14283104)
Calamari (Italian for squid) also derives from the same Latin root, via the ink connection.
Re:What will happen when we run out of names for JavaScript ... by kuzirashi on Saturday May 06, 2017 @04:59PM (#14282231)
Maybe the problem is real. :) Good luck with JS framework!
Re:What will happen when we run out of names for JavaScript ... by inopinatus on Saturday May 06, 2017 @05:02PM (#14282243)
Is there any particular reason not to use emoji? JavaScript is by specification a unicode language. I already have registered users in my system with pictographic name strings, why not software? Might be some introductory issues with logs and terminals and incorrect assumptions by developer tools, surely nothing we can't fix.
Re:What will happen when we run out of names for JavaScript ... by xg15 on Saturday May 06, 2017 @05:19PM (#14282320)
- Hey, I’m new to programming, which framework is the best for creating single page applications?

- Hello, I believe .js is the best, but at work we use .js for its speed and flexibility. Other popular choices are .js, .js and .js. Hope I’ve helped!

- That’s great! Thanks a lot!

Well, at least it's shorter, so there's that..

edit: Ok, that's the reason...

Re:What will happen when we run out of names for JavaScript ... by inopinatus on Saturday May 06, 2017 @05:31PM (#14282374)
That's not a reason not to use emoji. That's a reason to drag an ASCII-centric communications medium into the Unicode era. We're in an time where application data is Unicode. You may wish to paste such data into a chat, or refer to people and organisations whose names aren't written in latin script.

When your chosen comms medium doesn't support those things, it should be updated.

Re:What will happen when we run out of names for JavaScript ... by beojan on Saturday May 06, 2017 @05:37PM (#14282404)
Let's imagine that was a transcript of a verbal conversation. How would you pronounce the emoji? Facial expressions?
Re:What will happen when we run out of names for JavaScript ... by inopinatus on Saturday May 06, 2017 @05:45PM (#14282433)
I've never been afraid to use interpretive dance in my presentations.

What actually happens: see Chinese. One broadly-speaking-unified set of logograms, 200 spoken dialects, of which a handful are widely adopted, and one has governmental primacy.

Re:What will happen when we run out of names for JavaScript ... by kuzirashi on Saturday May 06, 2017 @07:54PM (#14282986)
I've had Chinese lessons and even Chinese people have problems understanding each other for example because of voice and voice emotions are so important. I think Chinese language shouldn't be role model for what IT world should be. :)
Re:What will happen when we run out of names for JavaScript ... by inopinatus on Saturday May 06, 2017 @11:37PM (#14283716)
Oh, I agree, it's not a role model. I think it stands as an example of possible emergent outcome.
Re:What will happen when we run out of names for JavaScript ... by xg15 on Sunday May 07, 2017 @03:28AM (#14284315)
Obviously facial expressions combined with illustrating sound sequences to resolve ambiguities.

- Hello, I believe MEEP.js is the best, but at work we use MOOP.js for its speed and flexibility. Other popular choices are WEEEEE.js, BLEEEH.js and WEEOOHWEEHOOWEEBLUB.js. Hope I’ve helped!

- That’s great! Thanks a lot!

Re:What will happen when we run out of names for JavaScript ... by xg15 on Sunday May 07, 2017 @03:20AM (#14284293)
Indeed, there is never a valid reason not to use emoji.

(Though in this case, the communication medium is Hacker News. Shame on you, Hacker News!)

Re:What will happen when we run out of names for JavaScript ... by franciscop on Saturday May 06, 2017 @06:30PM (#14282606)
Fun thing; I named Umbrella JS that way when i realized that you can use unicode as javascript variable names AND I just happened to find that as the first one. So the initial library (a jQuery sustitute) was literaly `"UMBRELLA UNICODE"('selector')` (note: HN doesn't allow for the character). Of course sanity came back and when releasing something decent I changed the name back to "u('selector')"

See the character I mean: http://www.fileformat.info/info/unicode/char/2602/index.htm

Re:What will happen when we run out of names for JavaScript ... by kuzirashi on Saturday May 06, 2017 @07:55PM (#14282988)
Wow, that's curious! Did it work in JavaScript though? Or just in name of package? :)
Re:What will happen when we run out of names for JavaScript ... by franciscop on Sunday May 07, 2017 @07:04AM (#14284868)
I doesn't seem to work anymore! But it used to work as the library was using that in the beginning.
Re:What will happen when we run out of names for JavaScript ... by nxc18 on Saturday May 06, 2017 @07:44PM (#14282944)
Have you ever tried typing emoji? Or reading it? Or writing it? Or speaking it?

Go give a tech talk about .js but careful, don't want to confuse it with .js

Re:What will happen when we run out of names for JavaScript ... by terandle on Saturday May 06, 2017 @04:44PM (#14282153)
"JavaScript and its earlier version — Java..." ???
Re:What will happen when we run out of names for JavaScript ... by kuzirashi on Saturday May 06, 2017 @04:48PM (#14282177)
Have some distance and sense of humour man ; )
Re:What will happen when we run out of names for JavaScript ... by terandle on Saturday May 06, 2017 @04:53PM (#14282202)
The article was mostly serious until then. Wasn't expecting a satire piece, caught me off guard.
Re:What will happen when we run out of names for JavaScript ... by thethirdone on Saturday May 06, 2017 @05:18PM (#14282312)
Really?

It seemed pretty clear it was making jokes to me.

From just above the joke about JavaScript and Java:

> Whether they use it in their job or just to make coffee (coffee-maker).

> But it’s not normal rapper like Eminem, it’s more like:

or further above:

> Some describe its usage — like anti-ecological tree-kill, some not

> [Image of ducks/birds idk] JavaScript developers pictured trying to find their way around in node_modules directory :(

I never got a serious feel at all.

Re:What will happen when we run out of names for JavaScript ... by SimbaOnSteroids on Saturday May 06, 2017 @07:30PM (#14282896)
You forgot the biggest clue, the title.
Re:What will happen when we run out of names for JavaScript ... by kuzirashi on Saturday May 06, 2017 @05:01PM (#14282238)
Happy to hear. :) Hope you enjoyed!
Re:What will happen when we run out of names for JavaScript ... by 0x4a42 on Sunday May 07, 2017 @02:22AM (#14284177)
Read the title again.:)
Re:What will happen when we run out of names for JavaScript ... by josephorjoe on Saturday May 06, 2017 @07:42PM (#14282938)
At first, you can just start adding 'ly' to all new packages: reactly, reduxly, expressly, passportly.

When that doesn't work any more, start prefixing names with 'get': getmochaly, getasyncly, getunderscorely.

After that, you need to start requiring at least 2 numerals, 3 capital letters, and 1 punctuation mark: geTBab3!lY9, Ge!ax1OSly2, g3tW%b4acKlY.

What could be more natural than npm install --save-dev getBAB3l-prese!-sta&e-0ly ?

Re:What will happen when we run out of names for JavaScript ... by kuzirashi on Saturday May 06, 2017 @07:52PM (#14282979)
Thanks for pointing out another trends and predicting new one! You're the saviour of JS-mankind!
Re:What will happen when we run out of names for JavaScript ... by lemuurd on Saturday May 06, 2017 @05:30PM (#14282369)
next week on HN:

"Show HN: ćřàp - a JS framework to name your JS framework using UTF-32 characters"

Re:What will happen when we run out of names for JavaScript ... by kuzirashi on Saturday May 06, 2017 @07:56PM (#14282989)
Why not UTF-512? :)
Re:What will happen when we run out of names for JavaScript ... by kyled on Saturday May 06, 2017 @05:13PM (#14282295)
Namespaces solves this issue, no?
Re:What will happen when we run out of names for JavaScript ... by Vanit on Saturday May 06, 2017 @07:14PM (#14282808)
My thought exactly.
Re:What will happen when we run out of names for JavaScript ... by baron816 on Saturday May 06, 2017 @08:02PM (#14283016)
The real question here is, will the web, in anything resembling it's current form still exist in 20 years? 100 years? 1000 years? And if so, will it rely on ES2037, ES2117, ES3017? Books haven't changed much at all in the last 1000 years, and although it would be naive for us to expect the internet to say the same, there will likely still be a demand for fairly simple blogs and forums well into the future.
Re:What will happen when we run out of names for JavaScript ... by karmakaze on Sunday May 07, 2017 @05:50PM (#14287893)
Github.com will be the de facto canonical naming. It's already used in several language/packing systems, supported by others. And as the article points out, what other alternatives are there?

There are issues with this as is evident in Go projects using forks, etc which will have to get sorted out and evolve.

Re:What will happen when we run out of names for JavaScript ... by haburka on Saturday May 06, 2017 @05:15PM (#14282306)
The number of node packages there are is deceptive when it comes to measuring the js ecosystem. It's better to count how many packages are well referenced, which might be a number as low as 10k.
Re:What will happen when we run out of names for JavaScript ... by majewsky on Saturday May 06, 2017 @05:56PM (#14282475)
But even if the library is not used, once it's on NPM, the name is taken.
Re:What will happen when we run out of names for JavaScript ... by franciscop on Saturday May 06, 2017 @06:31PM (#14282609)
Not really, if a library is truly empty in NPM just contact NPM and they are nice enough and will give you the name if you are going to use it.
Re:What will happen when we run out of names for JavaScript ... by makenova on Saturday May 06, 2017 @07:39PM (#14282926)
You can scope modules under your name. e.g. `@makenova/panda`
Re:What will happen when we run out of names for JavaScript ... by DonbunEf7 on Saturday May 06, 2017 @04:58PM (#14282222)
Has anybody considered not having a single global repository of JS packages? (Also, as usual, has anybody considered just not doing this whole JS thing?)
Re:What will happen when we run out of names for JavaScript ... by niftich on Saturday May 06, 2017 @05:31PM (#14282373)
Perhaps you mean "has anybody considered having formal, hierarchical namespaces", an orthogonal concern to having or not having a single global repository (although the two can be coupled together by the community if they so choose).

To which the answer is yes [1][2][3][4].

[1] https://github.com/npm/npm/issues/798 [2] https://github.com/npm/npm/issues/5239 [3] http://blog.npmjs.org/post/116936804365/solving-npms-hard-pr... [4] https://docs.npmjs.com/getting-started/scoped-packages

Re:What will happen when we run out of names for JavaScript ... by kuzirashi on Saturday May 06, 2017 @05:03PM (#14282248)
Can you elaborate on this? What's the alternative to single global repository? By single global repository you mean NPM?
Re:What will happen when we run out of names for JavaScript ... by DonbunEf7 on Saturday May 06, 2017 @07:48PM (#14282964)
An example alternative is a ports tree. You have a repository which can build packages from descriptions. This repository itself is a formal parameter, so it can be replaced easily. It's also a basic filesystem structure that doesn't depend on external services directly in order to be queried. At this point in history, we are starting to become much more capable of federating basic read-only filesystems, so the availability of a simple ports tree (and any referent tarballs) are no longer depending as much on central authority servers.

In addition to the BSDs, this is how the Nix ecosystem manages its package repositories. There is (of course [0]) a singularly large repository, nixpkgs, but there are also forks which can vary greatly in appearance, from nixpkgs + custom packages, all the way to systems like Triton, which replace a lot of the fundamental repository structure. Nonetheless, they are largely interchangeable at the top level.

NPM would have to be distributed as a git repository, at the least, for this to be feasible.

[0] Why is there always a single large structure at the center of repositories of data? It's because data likes to aggregate as a side-effect of what some people call "network effects" or "economies of scale" or "Boyle's law", although I'm not sure that any of them cover it succinctly. The best introduction to this that I know of is the two-balloon experiment: https://en.wikipedia.org/wiki/Two-balloon_experiment

Re:What will happen when we run out of names for JavaScript ... by dragonwriter on Saturday May 06, 2017 @07:48PM (#14282961)
Separate uncoordinated repositories (which risks namespace collisions), or separate repositories with a rule effectively providing a system for assuring universally unique names, e.g., by prefixing project names with the identification of the repository responsible for the local uniqueness of the name.
Re:What will happen when we run out of names for JavaScript ... by paulddraper on Saturday May 06, 2017 @05:27PM (#14282355)
The alternative is many.

E.g. apt.

Re:What will happen when we run out of names for JavaScript ... by krapp on Saturday May 06, 2017 @05:37PM (#14282403)
Even PHP manages to get this right - Composer uses the Packagist repository as a default but just about any git or svn repo with a URL will do.
Re:What will happen when we run out of names for JavaScript ... by jaredsohn on Saturday May 06, 2017 @07:14PM (#14282805)
npm supports git urls, too (or the even shorter user/project#tag if it is from github)
Re:What will happen when we run out of names for JavaScript ... by manquer on Sunday May 07, 2017 @03:58AM (#14284385)
Composer also supports namespacing
Re:What will happen when we run out of names for JavaScript ... by shawnz on Saturday May 06, 2017 @05:41PM (#14282425)
Does apt allow you to have multiple packages with the same name from different repositories? I don't see how it solves this issue otherwise.
Re:What will happen when we run out of names for JavaScript ... by paulddraper on Saturday May 06, 2017 @05:50PM (#14282459)
No, it does not.

But I don't use the vast majority of apt repos.

I use a handful of well-curated ones with high-quality software, plus a handful for one-off packages.

In contrast, there's basically no limit to how much debris you can upload to npm.

Re:What will happen when we run out of names for JavaScript ... by kuzirashi on Saturday May 06, 2017 @07:57PM (#14282995)
There's a lot of problems with APT. :)
Re:What will happen when we run out of names for JavaScript ... by nsxwolf on Saturday May 06, 2017 @06:32PM (#14282613)
Drug companies seemed to have run out of names a while ago and have resorted to barely pronouncible strings of mostly consonants. Like Xeljanz and Viibryd.
Re:What will happen when we run out of names for JavaScript ... by mason55 on Saturday May 06, 2017 @06:33PM (#14282619)
The reason for that is there are all kinds of rules about what you can name your drug. Can't sound like anything else. Can't suggest any effects it doesn't have. Etc. Made up words are pretty much the only safe bet. From there you want to make up a word that's memorable and short so it stands out and people remember it.
Re:What will happen when we run out of names for JavaScript ... by kuzirashi on Saturday May 06, 2017 @07:45PM (#14282948)
Didn't know about such rules for drug naming. Clarifies a lot. Thanks for sharing.
Re:What will happen when we run out of names for JavaScript ... by bbcbasic on Saturday May 06, 2017 @05:33PM (#14282383)
26^30 = shitloads of possible names
Re:What will happen when we run out of names for JavaScript ... by majewsky on Saturday May 06, 2017 @05:57PM (#14282482)

  $ pwgen -A0 30 10
  exeetoothoohohghohmixeinaeyigh aethahpoquielainogeorobeephoul
  cofeaphiwaeleedohphechiefeozei ahsohleiyahzithaacheibiechahth
  udiekomieheecohshohmupahshaese zaewetohheethohbocoocheikaikei
  keemokeebeejahjoomaengiopahshe oochephaekiethaehahshieshahsai
  poufifohjohtohdaiceghaizoenais aizeephahkongairiecogheegoedie
I expect all of these to be taken on NPM tomorrow, now that I posted them. :)
Re:What will happen when we run out of names for JavaScript ... by bbcbasic on Saturday May 06, 2017 @05:59PM (#14282490)
exeetoothoohohghohmixeinaeyigh

I know that. That's a Welsh town.

Re:What will happen when we run out of names for JavaScript ... by dTal on Saturday May 06, 2017 @07:01PM (#14282751)
It is very improbably named then, since a) the top 5 letters found in Welsh placenames are N, L, A, E, and R, and b) there is no 'X' in Welsh.
Re:What will happen when we run out of names for JavaScript ... by kuzirashi on Saturday May 06, 2017 @06:16PM (#14282563)
These are great names!
Re:What will happen when we run out of names for JavaScript ... by gmiller123456 on Sunday May 07, 2017 @10:00PM (#14288772)
See also: Pheonix, I mean Firebird, oops I mean Firefox.
Re:What will happen when we run out of names for JavaScript ... by lucidguppy on Saturday May 06, 2017 @06:37PM (#14282636)
constonant-vowel-constonant-vowel-constonant-vowel-constonant
Re:What will happen when we run out of names for JavaScript ... by na85 on Saturday May 06, 2017 @07:14PM (#14282806)
The part of me that cares about my HN karma wants me to refrain from saying that I hope people stop making JavaScript frameworks well before we run out of names. JavaScript is a monstrosity that from a usability standpoint really has made the web worse and not better.

I would love a web without js tracking, scroll bar hijacking, browser back/forward hijacking, delayed modal popups, useless animations that bring my Oneplus 3T to its knees, etc.

I also would love a computing ecosystem where nodejs didn't enable every journeyman web designer to try their hands at bringing all that cruft to the desktop.

I find the UX improves significantly with noscript.

Re:What will happen when we run out of names for JavaScript ... by kuzirashi on Saturday May 06, 2017 @07:58PM (#14282999)
Oh, this is very uncommon point of view :) Be prepared to be eaten, you're on JavaScript grounds!