nodejs/node on Hacker News

…It's incredible slow to start a debugging session, making you feel miserable. See open issues like https://github.com/nodejs/node/issues/877 Instead of arguing in favor of JavaScript as the default language and software stack we should…

comment by wslh · 2015-09-24 · in JavaScript as default language and software stack

…concerns, node.js 4.0.0 incorporates the history of io.js. io.js defined 1.0.0 in early 2015. See https://github.com/nodejs/node/blob/master/CHANGELOG.md and search for 1.0.0

comment by kbutler · 2015-09-10 · in Node v4.0.0

https://github.com/nodejs/node/blob/master/CHANGELOG.md

comment by speg · 2015-09-08 · in Node v4.0.0

…given that it's tar'ing stuff up at the moment. The decision was made not to wait for it here - https://github.com/nodejs/node/issues/2522

comment by nathankunicki · 2015-09-08 · in Node v4.0.0

In case you are interested, `Function.prototype.bind` in V8 is implemented here: https://github.com/nodejs/node/blob/9fddd83cf9adf505bce2e237... https://github.com/nodejs/node/blob/9fddd83cf9adf505bce2e237...

comment by songgao · 2015-09-06 · in How JavaScript closures work under the hood

One issue to go: https://github.com/nodejs/node/issues/2516 A .bat file is holding up the whole thing!

comment by timdorr · 2015-09-04 · in Node.js v4 Release Timeline

…and several things have been done in that respect: * The io.js project joined the Node Foundation ( https://github.com/nodejs/node/issues/1664#issuecomment-1018... ). * Joyent transferred ownership of nodejs.org to the Linux Foundation (…

comment by gregmac · 2015-08-12 · in Future Node.js releases will be from the io.js repo

Misleading title, if you read the issue link that drunkcatsdgaf posted ( https://github.com/nodejs/node/issues/2327 ).

comment by RossDM · 2015-08-12 · in Future Node.js releases will be from the io.js repo

see: https://github.com/nodejs/node/issues/2327

comment by drunkcatsdgaf · 2015-08-12 · in Future Node.js releases will be from the io.js repo

Should be included in the next major ( which will get V8 4.5 I guess ) https://github.com/nodejs/io.js/pull/2221#issuecomment-12625...

comment by antouank · 2015-08-05 · in Io.js v3.0.0

…All in all, I think even io.js is still very conservative compared to how node was pre-0.10 [1]: https://github.com/nodejs/io.js/issues/643

comment by spion · 2015-08-04 · in Io.js v3.0.0

…etc) even though the directory didn't exist. Solution was to abort after the first failed stat(). https://github.com/nodejs/io.js/pull/1920

comment by kevinburke · 2015-07-22 · in How we took our tests from 100 seconds to 100ms

…companies who want to hire someone to work on node core at least a good amount of the time. See: https://github.com/nodejs/io.js#current-project-team-members

comment by Fishrock123 · 2015-06-01 · in Ask HN: Who wants to be hired? (June 2015)

…io.js branch, great for trademarks now being owned by the community. Mikeal has more details here: https://github.com/iojs/io.js/issues/1664#issuecomment-10054... Also great for jsdom (one of node's best features) soon running on node…

comment by nailer · 2015-05-13 · in Node.js and io.js are merging under the Node Foundation

Here is the release proposal https://github.com/iojs/io.js/pull/1532

comment by inglor · 2015-05-07 · in io.js 2.0 released

…Not sure what you're referring to about DTrace issues in IO.JS, could you provide some guidance? 0: https://github.com/iojs/io.js/pull/1023

comment by Joe8Bit · 2015-05-05 · in Node.js Foundation – Node.js and Io.js Convergence Repo

The V8 4.2 update adds support for Native Classes in JavaScript: https://github.com/iojs/io.js/issues/1393 Significant & controversial.

comment by secoif · 2015-05-05 · in Io.js 2.0.0 Released

…the top of virtually EVERY file in the repo for node. Someone removed all but one (6430 deletions) https://github.com/iojs/io.js/pull/311/files I can imagine this makes up for a portion of it.

comment by brandonb927 · 2015-05-05 · in Io.js 2.0.0 Released

…that gives you an overview of a project. LOC will always be a shitty metric for anything. [1] https://github.com/iojs/io.js/commit/56e4255382ad4d2426e0346... [2] https://github.com/iojs/io.js/pulse

comment by lugg · 2015-05-05 · in Io.js 2.0.0 Released

Changelog: https://github.com/iojs/io.js/blob/7c89c4c7acdaa2035ec42195a...

comment by _yfoe · 2015-05-05 · in Io.js 2.0.0 Released

There is an open pull request that adds "workers" to io.js, uses threads - https://github.com/iojs/io.js/pull/1159

comment by phpnode · 2015-04-03 · in Io.js community thoughts on reconciliation

There have been some intermittent Windows issues: https://github.com/iojs/io.js/issues/1005 Not Microsofts problem.

comment by ed_blackburn · 2015-03-29 · in Node.js Tools for Visual Studio

…came as a side effect of investigating what was needed and running into the megapatch in iojs ( https://github.com/iojs/io.js/pull/826 ) where they fixed the tls defaults affecting node 0.12's out of the box score. Let me know if you have…

comment by nailer · 2015-03-24 · in Getting an A+ on the SSL Labs test in Node.js and Io.js

…(once it starts shipping on Chrome stable, which is roughly 6 weeks after it's been created)" [0] - https://github.com/iojs/io.js/blob/v1.x/CHANGELOG.md [1] - https://chromium.googlesource.com/v8/v8.git/+/4.1.0.21

comment by dsp1234 · 2015-02-27 · in Io.js and Node.js reconciliation proposal

The io.js discussion, which provides more useful insight, is available here: https://github.com/iojs/io.js/issues/978

comment by fcanela · 2015-02-27 · in Joyent Node.js: Reconciliation with io.js

…some point (for example, after a week of not adding a catch handler). There is a discussion here: https://github.com/iojs/io.js/issues/830

comment by inglor · 2015-02-25 · in io.js 1.4 released – featuring debuggable ES6 promises

There is a short regression for https://github.com/iojs/io.js/issues/932#issuecomment-760226...

comment by inglor · 2015-02-25 · in io.js 1.4 released – featuring debuggable ES6 promises

Yes there was a short regression with libuv on macs, here https://github.com/iojs/io.js/issues/932#issuecomment-760226...

comment by inglor · 2015-02-25 · in io.js 1.4 released – featuring debuggable ES6 promises

…What's the deal? Edit: They force pushed to master to remove the release due to issues on OSX https://github.com/iojs/io.js/issues/932#issuecomment-760480...

comment by statenjason · 2015-02-25 · in io.js 1.4 released – featuring debuggable ES6 promises

…fix: https://github.com/joyent/node/blob/master/deps/v8/src/heap/... assuming this is the issue: https://github.com/iojs/io.js/pull/952/files#diff-1440e8305d... It is kind of annoying that the bug is embargoed...

comment by apaprocki · 2015-02-25 · in io.js 1.4 released – featuring debuggable ES6 promises

…In short - it was named 1.4 because of how NPM updated and because of the big features landing. [1] https://github.com/iojs/io.js/issues/932

comment by inglor · 2015-02-25 · in io.js 1.4 released – featuring debuggable ES6 promises

You can find them here: https://github.com/iojs/io.js/blob/v1.x/doc/api/process.mark... it'll take a bit longer until the website syncs. We're interested in feedback on how the event descriptions are phrased since there is some controversy…

comment by inglor · 2015-02-25 · in io.js 1.4 released – featuring debuggable ES6 promises

…manager. > And yet, 1.3.0 "broke" the way that urls are resolved with regards to trailing slashes: https://github.com/iojs/io.js/pull/278 Can you link to documentation of the old way? The way I understand it is that they fixed a bug. If…

comment by Touche · 2015-02-20 · in Coffeescript 1.9.0 contains a backwards incompatible change

…public API. And yet, 1.3.0 "broke" the way that urls are resolved with regards to trailing slashes: https://github.com/iojs/io.js/pull/278 If you follow SemVer — and I don't think that Io.js should, or have to pretend to — this must be…

comment by jashkenas · 2015-02-20 · in Coffeescript 1.9.0 contains a backwards incompatible change

Discussion on the same point: https://github.com/iojs/io.js/pull/278 From the discussion: "semver-major" label was removed because it is a bug fix: Node 0.10 has the new behavior, and also WHATWG compliance.

comment by jeswin · 2015-02-20 · in Io.js 1.3.0 released

…/github.com/laverdet/node-fibers/issues/203 [4] https://github.com/msgpack/msgpack-node/issues/20 [5] https://github.com/iojs/io.js/issues/456

comment by doublerebel · 2015-02-10 · in Joyent Moves to Establish Node.js Foundation

…io.js does not contain this commit, or any of the changes from this commit: https://github.com/iojs/io.js/search?utf8=%E2%9C%93&q=%22PAS...

comment by LukeB_UK · 2015-02-10 · in Joyent Moves to Establish Node.js Foundation

…of both graphs share the same data.) [1] https://github.com/joyent/node/graphs/contributors [2] https://github.com/iojs/io.js/graphs/contributors

comment by _greim_ · 2015-02-10 · in Joyent Moves to Establish Node.js Foundation

This should help you io.js contributors: https://github.com/iojs/io.js/graphs/contributors?from=2014-... node.js contributors: https://github.com/joyent/node/graphs/contributors?from=2014...

comment by smurfpandey · 2015-02-10 · in Joyent Moves to Establish Node.js Foundation

That is being tracked here: https://github.com/iojs/io.js/issues/456#issuecomment-730639... As a native module owner, I made mine work right away and it was work that I needed to do anyway for Node compatibility because changes in…

comment by apaprocki · 2015-02-07 · in Node v0.12.0 (Stable)

From https://github.com/iojs/io.js > Is it io.js or IO.js or iojs or IOjs or iOjS? > The official name is io.js, which should never be capitalized, especially not at the start of a sentence, unless it is being displayed in a location that…

comment by ryanatkn · 2015-01-14 · in Io.js 1.0.0

…use semver and apparently even seem to understand the concept of identifying non-stable versions: https://github.com/iojs/io.js/issues/28 But apparently "beta" equals "stable" to these people.

comment by stephenr · 2015-01-14 · in Io.js 1.0.0

Yes, lots of packages depend on "the JavaScript executable" being called node. Discussion: https://github.com/iojs/io.js/issues/43

comment by elisee · 2015-01-14 · in Io.js 1.0.0

…versioning (assuming you're talking about http://semver.org/ ), they're switching to it (see https://github.com/iojs/io.js/issues/28 ). Node.js uses MINOR even = stable, odd = unstable (which is not semver) and is still in 0.x even though…

comment by elisee · 2015-01-14 · in Io.js 1.0.0

It's for bin scripts such as NPM which refer to the executable directly. See here: https://github.com/iojs/io.js/issues/249

comment by solomone · 2015-01-14 · in Io.js 1.0.0

…It's more or less a fork of node or "spork" as they call it. The github repo is a bit more clear: https://github.com/iojs/io.js The main point seems to be that it's run on an open governance model: https://github.com/iojs/io.js/blob/v1.x/GO…

comment by tach4n · 2015-01-14 · in Io.js 1.0.0

…V8 engine, plus an "open governance model" as opposed to Joyent's domination of node.js prime. https://github.com/iojs/io.js Current Project Team Members ============================ Isaac Z. Schlueter Ben Noordhuis Bert Belder Fedor…

comment by mintplant · 2015-01-14 · in Io.js 1.0.0

Version 1.0.0 (Beta stability) The hell? Seems it's intentional: https://github.com/iojs/io.js/issues/251#issuecomment-694177...

comment by dsissitka · 2015-01-14 · in Io.js 1.0.0

…changelog from the latest stable Node version v0.10.35, including all changes from unstable v0.11: https://github.com/iojs/io.js/blob/v1.x/CHANGELOG.md Also of interest, the state of ES6 in io.js: https://github.com/seegno/io.js/wiki/The-st…

comment by elisee · 2015-01-14 · in Io.js 1.0.0

…using HN, where 50% of the users are using Lynx). [1] https://github.com/feross/webtorrent [2] https://github.com/iojs/io.js [3] http://www.theguardian.com/technology/2014/aug/17/technology... [4] Disclaimer: I work for famo.us. These are…

comment by blubbi2 · 2015-01-01 · in Ask HN: What are your predictions for 2015?