Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

IO.js – Evented I/O for V8 javascript

github.com

Post reply on HN
Print view View original

31–40 of 48 posts

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

#31

Post by skrebbel »

k__ wrote: post #13
girvo wrote: post #11

Earlier quoted context omitted.

> 1. Fixating on platform stability over project evolution That's... hardly a bad thing, in my humble opinion. The other language I use at work, PHP, is a case-study in what happens when you "evolve" a project willy-nilly with little regard to platform stability. Nowadays, it's better, because the community has become more involved in the process, so I can see what #2 and #3 are Bad Things™ however.

PHP? I had the feeling that much evolution happend from 1 to 5 but not much afterwards :\

Have you at all been paying attention? PHP 5.6 has namespaces, closures, lambdas, generators, autoloaders, traits, function argument splats, sane array literals - basically everything the authors ever saw in good use, anywhere.

There is hardly any difference between PHP 4 and 5, except internals. The only real big difference between PHP 3 and PHP 4 is a different class syntax.

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

#33

Post by misterdai »

I'm finding the situation with Node.js quite frustrating. There doesn't appear to be much communication as to what's going on with the project.

It's also odd that the Node Advisory Board was supposed to meet on the 20th (2014-11-20). Chris Williams tweeted that it was about to start [1] but no minutes have appeared and I can't find any mention of what happened during the meeting.

[1] https://nodejs.org/advisory-board/2014-11-06/minutes.html#mi...)

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

#34

Post by dmpk2k »

drderidder wrote: post #22
doublerebel wrote: post #12

Earlier quoted context omitted.

Yes, the forkers are doing themselves a disservice. Joyent is accused of not communicating with the community, and yet the forkers respond by also not communicating with the community [EDIT: they have refused multiple opportunities to comment, Joyent is publicly appearing to make a consolation effort]. If Node wants to be taken seriously by a broader range of companies, it should be stable. There are forkers on the J…

This has been brewing for a year and a lot of people in the community felt it was inevitable [1]. Plenty of early node people were never keen on Joyent's grab in the first place. The idea that the majority of core contribs are being uncommunicative is not really borne out by the growing community around node-forward and how open it actually is. They've set up live chat, a mentors list, help pages, given access to any…

Plenty of early node people were never keen on Joyent's grab in the first place.

Joyent funded Ryan Dahl, Isaac Schlueter and other committers since 2009 or 2010, before the majority of programmers had heard of node.js. And node.js is firmly under an MIT license. Were the developers supposed to live off kudos and instant noodles?

If that's a grab, I wish more businesses would do that. We should be encouraging more investment by companies in open source, so complaining about Joyent stepping up to the plate and giving significant financial help to node.js during the early phase is a bit much.

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

#35

Post by voodootikigod »

misterdai wrote: post #33

I'm finding the situation with Node.js quite frustrating. There doesn't appear to be much communication as to what's going on with the project. It's also odd that the Node Advisory Board was supposed to meet on the 20th (2014-11-20). Chris Williams tweeted that it was about to start [1] but no minutes have appeared and I can't find any mention of what happened during the meeting. [1] https://nodejs.org/advisory-board…

Sorry for the delay, it takes a while to polish the minutes and then gain consensus from the rest of the group about the final minutes. The US Holiday didn't help much either (as well as finalizing RobotsConf, life, etc) They are here now: https://github.com/joyent/nodejs-advisory-board/blob/master/...

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

#36

Post by espadrine »

_almosnow wrote: post #6

With the few forks and stances that everyone is taking now, I really hope that an amazing project like Node doesn't get f * up by becoming fragmented and multiple different "versions" appearing.

The most valuable piece that came out of the node project is libuv, and that is certainly not going away.

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

#37

Post by misterdai »

voodootikigod wrote: post #35
misterdai wrote: post #33

I'm finding the situation with Node.js quite frustrating. There doesn't appear to be much communication as to what's going on with the project. It's also odd that the Node Advisory Board was supposed to meet on the 20th (2014-11-20). Chris Williams tweeted that it was about to start [1] but no minutes have appeared and I can't find any mention of what happened during the meeting. [1] https://nodejs.org/advisory-board…

Sorry for the delay, it takes a while to polish the minutes and then gain consensus from the rest of the group about the final minutes. The US Holiday didn't help much either (as well as finalizing RobotsConf, life, etc) They are here now: https://github.com/joyent/nodejs-advisory-board/blob/master/...

Thanks Chris, probably read into the delay a little just because I could find any mention of the meeting actually taking place or not, apart from your tweet about it starting.

Understandable though with all the other stuff you've got going on. Cheers :)

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

#38

Post by cwmma »

benatkin wrote: post #17
stormbrew wrote: post #3

40 minutes, 8 points, got to the front page, and... why? Is there a story behind this fork?

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

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

#39

Post by k__ »

skrebbel wrote: post #31
k__ wrote: post #13

Earlier quoted context omitted.

PHP? I had the feeling that much evolution happend from 1 to 5 but not much afterwards :\

Have you at all been paying attention? PHP 5.6 has namespaces, closures, lambdas, generators, autoloaders, traits, function argument splats, sane array literals - basically everything the authors ever saw in good use, anywhere. There is hardly any difference between PHP 4 and 5, except internals. The only real big difference between PHP 3 and PHP 4 is a different class syntax.

Well, I switched from PHP to JavaScript, so, no lol.

I thought the class system was improved with 5 and was unusable with 4. At least that was what I read. I started with ... PHP 5.2

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

#40

Post by girvo »

k__ wrote: post #13
girvo wrote: post #11

Earlier quoted context omitted.

> 1. Fixating on platform stability over project evolution That's... hardly a bad thing, in my humble opinion. The other language I use at work, PHP, is a case-study in what happens when you "evolve" a project willy-nilly with little regard to platform stability. Nowadays, it's better, because the community has become more involved in the process, so I can see what #2 and #3 are Bad Things™ however.

PHP? I had the feeling that much evolution happend from 1 to 5 but not much afterwards :\

PHP 5.6 and what Facebook are doing with HHVM/Hack are (in the latter case, literally) entirely new languages than PHP4 or even pre-5.3, and with the PSR community standards body, Composer/Packagist and the massive amounts of interoperation between libraries nowadays, it's actually enjoyable to code in again :)
Post reply on HN