Skip to content
This repository was archived by the owner on Aug 16, 2022. It is now read-only.

Node js vs io js why the fork #153

Closed

Conversation

Lellansin
Copy link
Contributor

#125
不好意思各位 😭 最近一个月各种事,还要几天才能回归。先简单弄上来,各位帮忙 review 下


* 从 Joyent 的 Node.js v0.12 版本 fork 而来
* 与 npm 生态系统完全兼容
* 将采用尽可能快的新的 V8 版本
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

将尽可能快的采用新版本的V8

@popomore
Copy link
Contributor

popomore commented Apr 9, 2015

@Lellansin 改改就可以合了

把那几个 Merge 的 commit rebase 下

@Lellansin Lellansin force-pushed the node-js-vs-io-js-why-the-fork branch from 6dfda72 to 13d2ef8 Compare April 17, 2015 07:27
@Lellansin
Copy link
Contributor Author

@popomore @coderhaoxin 帮忙再过一遍?


#### **更新: 2015/2/27**

[Mikael](https://github.com/mikeal) 为了未来 ‘Node’ 重组 ‘Node.js’ 和 ‘io.js’ 已经在 io.js 的 issue 中发起了一个包括像技术管理、长期支持、版本控制和 WG结构(WG structuring) 的[‘和解建议’](https://github.com/iojs/io.js/issues/978)。
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

已经在 io.js 的 issue 中

前面貌似需要个 标点吧 😄

@haoxins
Copy link

haoxins commented Apr 17, 2015

+1 👍

@fengmk2
Copy link
Contributor

fengmk2 commented Apr 18, 2015

rebase 一下

nodejs#125
基础翻译

first review

根据 @coderhaoxin  的建议修改,并补充翻译

adjust order
@Lellansin Lellansin force-pushed the node-js-vs-io-js-why-the-fork branch from 13d2ef8 to 16f362e Compare April 19, 2015 06:56
@Lellansin
Copy link
Contributor Author

上次 rebase 成两个 commit 了,方便看翻译,是要 rebase 成一个 commit 吗,还是漏了什么?

@haoxins
Copy link

haoxins commented May 11, 2015

land ddae580 f0a400e

cc @popomore @fengmk2

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

Successfully merging this pull request may close these issues.

4 participants