171–180 of 277 posts
so now which apt repository to I use for node going forward?
Don't. I don't think Chris Lea is updating his anymore. Wget the tarball and tar -C /usr/local --strip-components 1 -xvf
https://github.com/nodesource/distributions/#installation-in...
The io.js fork and subsequent merge back into Node.js, including the birth of the Node Foundation, has been one of the best examples of the power of open source I have ever seen in action. The situation went from bad, to worse, to the best possible outcome, and that's remarkable to say the least. Congratulations to everyone involved and thank you for the hard work.
As somebody who uses Node only at the periphery of my role (for things like the Zombie browser, and SASS parsing) the massive instability has put me off from relying on it for anything core. Documentation is quickly out of date, libraries seem to have incompatibilities which only become obvious when they don't work, there's no 'recommended' approach for even basic tasks. I won't pretend I'm speaking for everyone, as…
Node has its place, and it's not for everything, but for quickly whipping together sturdy, flexible web APIs, it's great.
> ARMv6 32-bit Binary: Coming soon Is there more information on what's holding back this build?
The fact that the little Raspberry Pi building it is still...well, building it! :) https://ci.nodejs.org/job/iojs+release/168/nodes=pi1-raspbia... It does look like it's very nearly done though, given that it's tar'ing stuff up at the moment. The decision was made not to wait for it here - https://github.com/nodejs/node/issues/2522
Earlier quoted context omitted.
Don't. I don't think Chris Lea is updating his anymore. Wget the tarball and tar -C /usr/local --strip-components 1 -xvf
Not so, Chris Lea's PPAs are now part of Nodesource: https://github.com/nodesource/distributions/#installation-in...
Earlier quoted context omitted.
In that case "Node" is 20 years old, and "Ruby" (for web development) is 11 years old.
What? It's fair to say Ruby didn't take off until 1.8 which came out in 2003, but how in any way is Node 20 years old?
Earlier quoted context omitted.
For the benefit of any who are not sure what you are talking about, could you please elaborate on what some of these "better ways to handle that" are? It would make your comment much more helpful, IMHO.
Blocking threads. People associate threads with shared-memory concurrency, which can be really hard to deal with, but shared heaps are not the important part - blocking is. Blocking threads means that all your functions can call each other, all control flow constructs just work, and debugging is sane. With blocking threads functions don't need to belong to a special class of async functions that in general need to be…
Earlier quoted context omitted.
> I don't think most people working on Node want a Rails equivalent It wouldn't really be possible anyway. Async programming is hard and the shortcuts one can take with synchronous Ruby are impossible with Async Javascript. Nodejs has a "fibers" lib though , but it doesn't look like it is widely popular, but AFAIK it is the only to truly abstract async programming.
Using abstractions like http://koajs.com/ and https://github.com/tj/co make Node code feel like every other language. var user; try { user = yield db.insertUser('foo') } catch(err) { if (err.code === '23505') { this.flash['error'] = 'Username taken'; this.redirect('/register'); return; } throw err; }
Earlier quoted context omitted.
$ cat /etc/issue Ubuntu 14.04.3 LTS \n \l $ apt-cache showpkg nodejs | head Package: nodejs Versions: 0.10.25~dfsg2-2ubuntu1 (/var/lib/apt/lists/us.archive.ubuntu.com_ubuntu_dists_trusty_universe_binary-amd64_Packages) (/var/lib/dpkg/status) My package manager knows nothing of this mythical "bleeding edge" of which you speak...
Probably your best bet at this point is to use the NodeSource repos to keep up to date with the latest (stable) versions: https://github.com/nodesource/distributions
Guys, does V8 still deoptimize on ES6 features? For example, would using say const/lets in a function prevent V8 from optimizing it as a whole? That was the case some time ago when these features were still under a flag.
Earlier quoted context omitted.
> Your latter paragraph seems a bit fuddy as people 'just dipping in and out' would never have to have contended with the iojs 'name' any more than Python/Ruby/PHP people have to switch to a different VM every time one is announced (e.g. PyPy/Rubinius/Hack). One of my main use cases for Node is Zombie, and that required io.js after v3. No mainstream PHP, Ruby or Python application has required a different interpreter…
Sounds to me like your issue is with the author of Zombie.