|
|
|
|
|
|
by mike_ivanov
4133 days ago
|
|
|
That doesn't tell me anything. It assumes the reader is somehow familiar with the context and shares the authors' sentiment, although that is not true. This is what should be explained there: 1. What is the problem with Node.js? 2. What is wrong with Joyent? 3. Why the fork was the only adequate solution? 4. How come this is beneficial (and not harmful) to the community? 5. Is it a drop-in replacement? How does it affect existing projects? 6. How the future looks like from this point of view? However hard I look at that paragraph in Readme, I still can't see these questions answered. Edit: typo |
|
|
1. answered by readme & faq (predictable release cycles)
2. answered by readme & faq (open source governance)
3. nonsensical question (who said io.js is the only adequate solution?)
4. loaded question
5a. mostly, look at the ES6 page or just try it out
5b. obviously no simple answer
6. subjective question. It looks bright to me.