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

Io.js 1.0.0

iojs.org

Post reply on HN
Print view View original

101–110 of 190 posts

Re: Io.js 1.0.0

#101

Post by Kiro »

silversupreme wrote: post #27
mintplant wrote: post #16

Earlier quoted context omitted.

It's a fork of node.js with ES6 support. The goal is a faster release cycle and an updated 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 Indutny Trevor Norris Chris Dickinson Colin Ihrig Mikeal Rogers Rod Vagg

I find Ben's inclusion on this list interesting, given his history with Joyent/the node community.

What happened?

Re: Io.js 1.0.0

#102

Post by albertoleal »

jkrems wrote: post #92
tlrobinson wrote: post #90

Earlier quoted context omitted.

What is 'the "synchronous require" problem'? I've never run into issues with the CoffeeScript require hook, for example.

With a lot of files app startup can be delayed and the event loop be blocked. Which messes with timeouts among other things. The problem is that each file is loaded from disk and parsed in series without any level of parallelism (no real way around that in a pre-ES6 world). With CoffeeScript you put the time it takes to compile to JavaScript on top of that. If you have a big app with a lot of CoffeeScript files, it m…

See: https://github.com/sebmck/roadrunner

Re: Io.js 1.0.0

#103

Post by fergie »

quaunaut wrote: post #10

...Okay, normally I roll my eyes at people asking "What does this do" but Christ this is ridiculous. From the FAQ: > What is io.js? > io.js is a JavaScript platform that is compatable with Node.js & npm. What does that even mean? Edit: Thanks for those answering. I started figuring out what it was, but sometimes folks really need to learn that "A correct definition" is not the same as "a useful definition". However,…

io.js is a program that makes JavaScript run on a server.

io.js is a fork of node.js but is "better" because:

1) io.js always uses the latest JavaScript engine.

2) io.js is not controlled by private interests.

Re: Io.js 1.0.0

#104

Post by bshimmin »

_greim_ wrote: post #42

I suspect there will be a split in the npm ecosystem now, not so much along node/iojs lines but along es5/es6 lines. There's already been lots of discussion about whether module builders should publish es6 code, or should everything be transpiled down to es5 code in order to keep the ecosystem unified (the unspoken caveat being, around es5). I think es5 is a dinosaur as of today, so I say go ahead and publish es6 cod…

I don't think you can really call something "a dinosaur" when the standard that is supposed to supersede it hasn't even formally been published yet!

Re: Io.js 1.0.0

#105

Post by stephenr »

secoif wrote: post #36
nubela wrote: post #3

How does a 1.0.0 translate to beta-stability build?

Node is moving to semantic versioning: http://semver.org/ In this scheme, version number is not an indicator of stability.

Semver specifically stipulates that pre-1.0.0 is for unstable work.

> Major version zero (0.y.z) is for initial development. Anything may change at any time. The public API should not be considered stable.

It also allows for identifiers/metadata after the version eg 1.0.0-alpha or similar.

It also specifically says:

> Version 1.0.0 defines the public API.

Re: Io.js 1.0.0

#106

Post by stephenr »

elisee wrote: post #9
nubela wrote: post #3

How does a 1.0.0 translate to beta-stability build?

As I understand it, the io.js devs think Node.js should have switched to 1.x ("stable") a long time ago. But from their perspective, this is io.js's first release with their own build infrastructure and they made a lot of aggressive changes (updated V8 dependency, etc.), so they're calling their own release beta-quality. Makes sense?

It doesn't make sense to release beta quality software as "v1.0.0" without any reference to being a beta in the version itself. Either use a 0.x version or use a -beta -identifier if the api is fixed but stability is not guaranteed

Re: Io.js 1.0.0

#107

Post by reitanqild »

k__ wrote: post #44
dsissitka wrote: post #6

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

Doesn't 1.0.0 simply mean, API stability?

An explanation about the downvotes would be appreciated. Thanks.

Re: Io.js 1.0.0

#108

Post by CmonDev »

fergie wrote: post #103
quaunaut wrote: post #10

...Okay, normally I roll my eyes at people asking "What does this do" but Christ this is ridiculous. From the FAQ: > What is io.js? > io.js is a JavaScript platform that is compatable with Node.js & npm. What does that even mean? Edit: Thanks for those answering. I started figuring out what it was, but sometimes folks really need to learn that "A correct definition" is not the same as "a useful definition". However,…

io.js is a program that makes JavaScript run on a server. io.js is a fork of node.js but is "better" because: 1) io.js always uses the latest JavaScript engine. 2) io.js is not controlled by private interests.

Really? I thought V8 makes JavaScript run on a server.

Re: Io.js 1.0.0

#109

Post by CmonDev »

monkey_slap wrote: post #11
quaunaut wrote: post #10

...Okay, normally I roll my eyes at people asking "What does this do" but Christ this is ridiculous. From the FAQ: > What is io.js? > io.js is a JavaScript platform that is compatable with Node.js & npm. What does that even mean? Edit: Thanks for those answering. I started figuring out what it was, but sometimes folks really need to learn that "A correct definition" is not the same as "a useful definition". However,…

I still cannot figure out what this actually is besides Javascript

It's an implementation of the Reactor Pattern with some package management capability. Not a platform. Not a framework. Not an engine. Just a script.
Post reply on HN