More

Fishrock123 · on Oct 30, 2015

"V8 Major versions"

actualprogram · on Oct 30, 2015

io.js made a lot of noise about this, and has reached a "compromise" position that is indistinguishable to the end-user - or is LTS going to take V8 version bump over its 2.5-year life?

No?

Then take your scare quotes and bang your drum elsewhere, because from where I stand, the new boss is pretty much the same as the old boss.

Fishrock123 · on June 4, 2015

Haha, that was fun. :P https://twitter.com/minetweeter_/status/606481421633482752

Fishrock123 · on June 1, 2015

Location: Canada

Remote: Must for at least short-term

Willing to relocate: probably not, not to USA

Technologies: Node.js + all related things js

Portfolio/Resume: https://searchbeam.jit.su/about

Email: fishrock123 at rocketmail dot com

I'm part of the Node.js TSC and looking for 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

Fishrock123 · on June 3, 2015

Recruiters: No thanks.

Fishrock123 · on Feb 20, 2015

npm stands for "no problem meatbag", not "node package manager" ;)

It's the package manager for javascript and will continue to be. The module system in io.js is not going to be changing anytime soon.

Fishrock123 · on Feb 3, 2015

Yes. It is arguably larger news for io.js.

However, that io.js ships with v8 4.1 is quite a large step ahead for dependants, not just for language features, but also under-the-hood stability and performance.

Of course, there is also everything that node 0.11.x has, plus a release schedule to match Atom's own release cadence. :)

vacri · on Feb 3, 2015

io.js also ships with the node.js active core developers...

Fishrock123 · on Jan 21, 2015

For posterity to anyone who still reads this, the spork thing is mostly my fault. And it sort of caught on.

I do website and irc stuff for io.js and I had trouble describing what the project was in relation to node.js.

So I called it a spork, because "sporks are friendlier". Whatever that means. Aside from being friendly.

Proof is somewhere in the io.js irc logs back near when the project sporked.

http://logs.libuv.org/io.js

Fishrock123 · on Dec 4, 2014

More info will be added shortly to http://iojs.org/ See also http://nodeforward.org/

There is a lot going on, and it is a little difficult to keep track of everything, for sure.

Just know that io.js will be node and npm compatible.

Fishrock123 · on Nov 20, 2014

I would like to mention that Netflix could have consulted the express maintainers (us) but didn't.

Source: myself - https://github.com/strongloop/express/pull/2237#issuecomment...

Fishrock123 · on June 9, 2014

This also needs to be available for commit threads, I think.

See: https://twitter.com/Fishrock123/status/476133688506609664

Fishrock123 · on Feb 11, 2014

Using this framework right now -- it is quite excellent. Full of features, and with great, constant support.

Also, it runs ontop of the Pixi.js renderer, meaning it is super, super fast.