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

151–160 of 190 posts

Re: Io.js 1.0.0

#151

Post by jdc0589 »

tlrobinson wrote: post #95
jkrems wrote: post #92

Earlier quoted context omitted.

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…

I don't see that being an issue for the vast majority of Node.js programs, i.e. long-running servers.

define "issue".

will it impede functionality? probably not. will it add precious time to server process start time? definitely, especially if the problem gets compounded.

Re: Io.js 1.0.0

#152

Post by [deleted] »

benihana wrote: post #137
duncanawoods wrote: post #98

In their words, io.js is "A spork of Node.js with an open governance model". Hmm. Lets hope the spork gets spooned so that no projects get knifed. If not then I guess we have to hope for a knork so we don't get stuck with a couple of chopsticks. Glossary Forking : Creating a fork to intentionally diverge from main-line development. Spooning : Merging a fork back into the main line of a project Sporking : Creating a f…

groan Don't get me wrong, thanks for the information. But seriously. It's like when you come up with a whimsical naming scheme for your home network devices and you get trapped in that naming scheme and have to come up with more and more obscure Lithuanian folk demons that fit into your conventions and it becomes a parody of itself and you're not sure if you're serious or joking anymore.

[deleted]

Re: Io.js 1.0.0

#153

Post by tootie »

mintplant wrote: post #16
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,…

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

Are node/io permanently joined to V8? I know that Oracle has been putting some effort into getting Avatar.js to be fully compatible with node and run on the JVM, but it isn't gaining much traction.

Re: Io.js 1.0.0

#154

Post by TazeTSchnitzel »

drderidder wrote: post #149

Node got forked because it got corped. When a corporation sinks their hooks into an active open source project, it's only a matter of time. Mysql, Maria, Hudson, Jenkins... same story. io.js is the way forward, and congrats to the core team.

Plenty of corporations have successfully managed open-source projects.

Re: Io.js 1.0.0

#155

Post by longlivegnu »

CmonDev wrote: post #108
fergie wrote: post #103

Earlier quoted context omitted.

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.

V8 is just a JS engine, it is used in io.js, node.js, chrome, and chromium.

Re: Io.js 1.0.0

#158

Post by grandalf »

robinricard wrote: post #145
grandalf wrote: post #140

Any advice on whether it's better to use ES6 or Coffeescript?

First of all they're not the same thing. Coffeescript transpiles to JS (ES3 or 4 if I remember well) and ES6 is a new standard (not finished yet). Maybe one day coffee may compile to ES6 (but that's not likely since that would break support with older browsers). As said before, ES6 may reduce the need of transpiled languages but won't replace them. From my point of view, ES6 will never replace ClojureScript nor TypeS…

Thanks -- that meshes with my impression so far. Is it smart/reasonable to use the es6 shim today?

Re: Io.js 1.0.0

#159

Post by jkrems »

tlrobinson wrote: post #95
jkrems wrote: post #92

Earlier quoted context omitted.

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…

I don't see that being an issue for the vast majority of Node.js programs, i.e. long-running servers.

As I said: there's no guarantee it affects you. But messing with timeouts during startup (where stuff might be failing and prevent server processes from recovering correctly) can be an issue. Even when the process is long-running in general. If that issue affects your particular program is a different question.

Re: Io.js 1.0.0

#160

Post by _greim_ »

wycats wrote: post #56
_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…

Important to note: because JavaScript itself is always backwards-compatible (1JS), any code that runs on Node will run on iojs, but not necessarily vice versa. That means there need not be a split in the ecosystem: people who want maximal coverage can target ES5, while people who want the latest features can target ES6. Unlike the browser, however, where people can't control their runtimes, I suspect there will be mu…

> We're liberated on the server.

I'm liberated on the server in my own app, but not necessarily if I'm publishing something for everyone to use. In that case I'm either forced to feature-detect my way along, or target certain engines. The reason I think the latter will happen is devs to whom node was an escape-hatch from client-side hell will loathe the idea of going back. E.g. [1]

[1] https://twitter.com/brianleroux/status/554753200503271424

Post reply on HN