phpnode

AFAIK joyent have never once mentioned io.js in their communications, apart from to say "ha ha, what's that?"

It actually had nothing to do with the pronouns or the angry mob, and everything to do with forcing a StrongLoop employee out.

Is this sarcasm? io.js would not exist if joyent hadn't made significant mistakes, e.g. failing to ship a new release for years, also this political point scoring alienated a lot of people - https://www.joyent.com/blog/the-power-of-a-pronoun

These kind of posts rather grate on me. OOP is a useful tool a lot of the time and sometimes it isn't, in this way it is identical to FP.

The whole problem is that people really like absolute statements, X bad, Y good. But the real world is no where near as simple as that.

This is really great!

Refusey DO YOU REFUSE? We're refusing to drive things that matter.

http://tiffzhang.com/startup/index.html?s=61244441196

offtopic - I've seen a number of blog posts using this hand drawn diagram style recently, does anyone happen to know how it's done? (answers other than "by hand" appreciated)

There is an open pull request that adds "workers" to io.js, uses threads - https://github.com/iojs/io.js/pull/1159

The zip files on that page contain the source for kdb, I thought I'd take a look at how it works.... nope! That is impenetrable

no, he isn't:

> "To go out and buy new engines for the B-52, you'd have a really hard time fitting that into our program, but that's why we're interested in a public-private partnership, which would be a different way to amortize those engines over time and pay for them in the savings that they actually generate, instead of paying for them out of savings that you hope for.

This sounds like a Private Finance Initiative as the GP mentioned

@dang why was this thread censored?

> Also, is it a good idea to connect a machine that has an unprotected operating system to the internet?

If the operating system has no IP stack or networking of any kind then it's probably ok

Would you trust those benchmarks if they did? Much better that a third party creates them

Context: http://antirez.com/news/87

Your email address isn't listed in your profile (you might have entered it in the "email" box, but that's not visible to other people)

It looks like videos will be published "shortly", I wasn't there but I'd imagine there was some cross over with this post: https://groups.google.com/forum/#!search/a/redis-db/PxFeA0fH...

The guy is pretty passive aggressive in that thread which makes it hard to take his points seriously.

Well that sounds like a very dubious move from Matt Stancliff, I wonder what the rationale was.

Edit - particularly galling given this graph https://github.com/antirez/redis/graphs/contributors

I do occasionally glance at KIA, and frankly it is terrifying. There are a lot of angry, naive people there.

This is the same kind of deluded apologism that the gamer gate crowd uses and it is dangerous. How can anyone judge the credibility of a threat made by a stranger on the internet? A threat is a threat.

> LOVED BY 41169 DEVELOPERS

Where does this statistic come from? I only see 196 stars on github at https://github.com/Irrelon/ForerunnerDB

No, it shouldn't be surprising, but they are not correct, because bob is my name (it isn't).

No, the official name for io.js is io.js, it is explicitly not Io.js. You can tell because this is what the owners of the project have clearly stated. Linguistic rules (which are rarely in fact rules), have nothing to do with it. If I tell you my name is "bob" and not "Bob" then I'm right because it's my name, you don't get to enforce your own preferences, just because of the language you speak.

It's copied from the linux kernel - http://www.linfo.org/kernel_version_numbering.html

I think not:

> if your software is being used in production, it should probably already be 1.0.0. If you have a stable API on which users have come to depend, you should be 1.0.0. If you're worrying a lot about backwards compatibility, you should probably already be 1.0.0.

yeah, node doesn't do this. node 0.12.0 should actually be (at least) node 5.0, if they followed semver.

HN auto-capitalizes story titles, because it presumes to know better than the submitter.

> Callbacks allow await/defer in Iced CoffeeScript

Not the same thing as in ES6, also that project is totally dead.

> generally devs just end up creating long chains of anonymous functions rather than long nests of anonymous functions

Not true in my experience, also not required at all when using async / await.

> Promises actually discourage flat code (and functional programming) for that reason.

This is really not true, Promises are functional and composable, callbacks are imperative.

> I understand they seem attractive but become a hack in complex situations.

Just no. Callbacks lead to terrible "solutions" like caolan/async, callbacks make refactoring extremely awkward.

Callbacks don't even get to claim better performance, because they require a load of internal hacks in node/io.js to maintain state.

With async/await in the picture, callbacks so totally inferior I can't believe someone would attempt to argue otherwise.

please stick with promises. Promises are the only sane way to deal with async in JS. With people starting to use async/await they become even more compelling.

The people who defend callbacks either don't understand the benefits that promises provide, don't know about async/await or are suffering from stockholm syndrome.

Callbacks do not pass the reversibility test. If everyone had started out with promises and / or async/await, and someone proposed callbacks as a way to deal with this instead, they'd be dismissed as a fool. They're an accident of history and we should forget about them as quickly as possible.

catching up? io.js is waaaaay ahead of node both in terms of features and community engagement

Redis.io already does this fwiw