IO.js – Evented I/O for V8 javascript • Hacker News Board

Re: IO.js – Evented I/O for V8 javascript

#41

Post by benatkin » Mon, Dec 01, 2014, 9:11 PM UTC

cwmma wrote: post #38

benatkin wrote: post #17

Earlier quoted context omitted.

There doesn't appear to be much of one, yet. The latest commit by indutny was just a commit to node that the owner of the iojs GitHub organization pushed to GitHub. There are no public members of the iojs organization. Even the name of the repo, "evented I/O for v8 javascript" is the same. All that's been introduced here is a new name, io.js.

from the issues that have been opened [1] and closed [2] it looks like indutny, jonathanong, and rvagg are involved, aka all people involved with node forward 1. https://github.com/iojs/io.js/issues/5 2. https://github.com/iojs/io.js/issues/7

Yes this appears to be the main thing at play right now. A small number of serious node hackers are contributing to io.js. This could be big, but it's too early for me to tell.

Re: IO.js – Evented I/O for V8 javascript

#42

Post by kylequest » Wed, Dec 03, 2014, 5:55 PM UTC

If you are curious about node-forward vs io.js take a look at the end of this page http://nodeforward.org to see how they are related :-)

Re: IO.js – Evented I/O for V8 javascript

#43

Post by throwaway90447 » Thu, Dec 04, 2014, 9:24 PM UTC

scljstcwombat wrote: post #20

It's raining node forks: https://github.com/io-forward/io-forward

Fork Yeah!

Re: IO.js – Evented I/O for V8 javascript

#44

Post by Pharohbot » Fri, Dec 05, 2014, 5:52 PM UTC

Bahamut wrote: post #28

logicchains wrote: post #21

Earlier quoted context omitted.

Or Dart. It's a lot closer to node and JS than Go (it uses asynchronous IO), and can more easily be used across both the server and client (Go's compilation-to-Javascript support is less developed). It's also surprisingly fast for a dynamic language, and has the generics Go lacks.

Should also mention that Dart is faster than Node - it benefits from Google's development of V8, and the language design was built for optimization while taking a lot of the good parts from JS.

V8 Turbofan using asm.js AOT that is in beta right now otherwise.

Re: IO.js – Evented I/O for V8 javascript

#45

Post by jackbravo » Fri, Dec 05, 2014, 6:04 PM UTC

@Mikeal has a couple of posts on the subject:

- https://medium.com/@mikeal/on-corporate-ownership-of-open-so... - https://medium.com/node-js-javascript/fragmentation-7e87d28f...

Re: IO.js – Evented I/O for V8 javascript

#46

Post by almogK » Fri, Dec 05, 2014, 6:45 PM UTC

I think it comes down to politics, I feel its always better to have a company run and support an open source framework as long as their listen to the community and letting the community be a part of the framework.

Re: IO.js – Evented I/O for V8 javascript

#47

Post by scljstcwombat » Sat, Dec 06, 2014, 2:39 AM UTC

jackbravo wrote: post #45

@Mikeal has a couple of posts on the subject: - https://medium.com/@mikeal/on-corporate-ownership-of-open-so... - https://medium.com/node-js-javascript/fragmentation-7e87d28f...

Ah yes, Mikeal, whose capability of double-think is so well-developed that he can claim to not understand what "fragmentation" means while at the same time advocating to do precisely that - https://github.com/iojs/io.js/issues/9

I swear Chris Dickinson is the only sane one in this whole mess. Possibly because he's new. Possibly because his employer is the only one involved that's not beholden to VC money and expectations of return.

Re: IO.js – Evented I/O for V8 javascript

#48

Post by elixir1 » Sat, Dec 06, 2014, 3:00 AM UTC

As a dev do we continue to use node or change to the fork?