Skip to content
This repository has been archived by the owner on Nov 21, 2018. It is now read-only.

"npm compatible platform"? #46

Closed
Daniel15 opened this issue Jan 14, 2015 · 3 comments
Closed

"npm compatible platform"? #46

Daniel15 opened this issue Jan 14, 2015 · 3 comments

Comments

@Daniel15
Copy link

Migrated from nodejs/node#365:

Someone linked me to your project site today so I thought I'd take a look. The first thing I read was "io.js is an npm compatible platform originally based on node.js™" which confused me and I had no idea what this meant. What does "npm compatible platform" mean here? Is PHP a "Composer compatible platform" and is Python a "PyPI compatible platform"?

It would have made much more sense if it said "JavaScript runtime" or something like that. Perhaps "io.js is a JavaScript runtime with a Node.js-compatible API".

@snostorm
Copy link
Contributor

This is good feedback @Daniel15, thanks. (I'm not in love with the copy that's there myself.)

Let's compare:

Node.js® is a platform built on Chrome's JavaScript runtime for easily building fast, scalable network applications. Node.js uses an event-driven, non-blocking I/O model that makes it lightweight and efficient, perfect for data-intensive real-time applications that run across distributed devices.

^ Much clearer.

Side thought: continuing to flush out the homepage copy and expand the homepage in general to include more content like "example code blocks" or top/unique features is another thing that can help explain the project :)

@mikeal
Copy link
Contributor

mikeal commented Jan 14, 2015

I actually hate that description of Node.js :)

It does nothing to describe what people actually use the software for and actually distracts from some of the primary uses (front-end tooling).

The reference to npm is also a link to npmjs.org which provides context. At this point in time more people know about npm than io.js. If you know about neither you'll get a better idea of what io.js can do by visiting npmjs.org than by using words like "non-blocking io."

@snostorm
Copy link
Contributor

@Daniel15 I am going to move the discussion on this to #53 as it is a meta issue regarding communicating what io.js in general. Thanks again for passing along the feedback.

@mikeal I'm not saying I'm in love with Joyent's description, but at least it gives more insight than what is online at iojs.org right now.

Let's continue brainstorming on #53 and on the related PRs.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants