Repository navigation
Is it io.js, IO.js, or something else? #118
Description
Activity
I've been using it as lowercase
LOL, damn i was hoping it would be
iO.JsiOo.oOo.jsThis should clarify it nodejs/build-containers#5 (comment)
@mathiasbynens I think it would be fine to have this in the documentation, unless the TC disagrees.
going to flag this as a discussion for TC this week
iOo.oOo.js
That's gotta be a close second.
That was just how izs used it, doesn't make it the official approach.
On Tue, 9 Dec 2014 9:07 am Ching-Han Ho notifications@github.com wrote:
IO.js.
http://blog.izs.me/post/104685388058/io-js
—
Reply to this email directly or view it on GitHub
#118 (comment).The reverse name (jsio / js.io) had been swimming in my brain for a few days (and then I finally searched the name and realized it was already a thing.) So my €0.02: IO.js.
I do wonder if, over time, there is a risk of the "js" dropping when the project is discussed in more colloquial use and people just calling it IO/io.
Per today's TC meeting, it's "io.js". All hail io.js!
🤘
Let’s document this in the README (or in a FAQ somewhere).
@isaacs Could you run
s/IO.js/io.js/gon your blog post to reduce confusion?- added a commit that references this issue
on Dec 12, 2014 - added a commit that references this issue
on Dec 7, 2015 - added a commit that references this issue
on Apr 6, 2017
The main contributors to this repository seem to use “io.js” (in issues, commits, meeting notes), but @isaacs’ blog post has “IO.js”. Which is it?
Let’s nip this in the bud and add this FAQ to the README.
cfr. https://www.npmjs.org/doc/misc/npm-faq.html#is-it-npm-or-npm-or-npm-