-
Notifications
You must be signed in to change notification settings - Fork 129
Wording & project description #2
Comments
rewording the 2nd line could read:
|
"io.js is a javascript runtime compatible with modules published to npm." Avoid the term fork, or spork for that matter. "Initial release is planned for January 13th." and link to the Issue. |
yes, io.js description is much better than the release line I tried to reword. |
Disclaimer: This is an unofficial post by a random person from the community. I am not an official representative of io.js. Want to ask a question? open an issue on the io.js - what you need to know
|
The thing is, I don't really think of io/node as a runtime. That's what V8 is. Honestly, we do need to tell people this is the same codebase somehow, and that's what a fork is. But I'm sure we can settle for "knife", "shiv", or "culinary instrument". :D |
@Fishrock123 s/runtime/platform |
@Fishrock123 what?! |
@reqshark talking this much about "node.js" fuels speculation. I know that we have to address the relationship but the messaging should be more about what "io.js" is and not just about "node.js" A good metric is, will this messaging still be relevant a year from now? |
@mikeal i couldn't agree with you more, keep it focused on the future |
At the same time, people still need to know things relative to now. |
What is the precise meaning of totally compatible? Does this mean that io.js has already decided what it will never do, or is this promising something that is incompatible with the forward intent? |
s/totally/fully |
So, will the executable be |
It's "npm package manager". No rename needed. :P |
npm: no problem meatbag |
Improved, could still use work maybe. I still think we should mention it is node-compatible, for now. @mikeal thoughts? |
I also think that the site should explain how open gorvenance model works in iojs, or at least provide a link explaining what it is. Is this wikipedia article right for this purpose? |
I'm going to link to the document once it lands in core: nodejs/node#22 |
Regarding a discussion that was had in irc, I'm suggesting we change "spork" to "dinglehopper":
New Tagline Would Read:
|
@codevinsky +100000 |
lol yeah, that's the best idea to avoid "fork" term :D |
Will close with #27 |
(tagline)
(description)
Discussion appreciated. :)
See also: nodejs/node#3 and nodejs/node#24
The text was updated successfully, but these errors were encountered: