Fork go code into a new repo

[mrares]

Fork go code into a new repo

[dgryski]

Depends how much effort we want to put into checking cross-compatibility, or if we plan to deprecate the node.js version.

[mrares]

I absolutely do not want to deprecate the node.js version, no cares about cross-compatibility. I strongly think the node.js version is an excellent test-bed for ideas, more so than the go version due to developer accessibility to the language, and should go forward as that.

[ikruglov]

I see no reason at forking go version because we prototype with it as we prototype with nodejs. But if you insist I also see no problems of doing it.

On 18 Nov 2015, at 13:51, Rares Mirica [email protected] wrote:

I absolutely do not want to deprecate the node.js version, no cares about cross-compatibility. I strongly think the node.js version is an excellent test-bed for ideas, more so than the go version due to developer accessibility to the language, and should go forward as that.

—
Reply to this email directly or view it on GitHub.