I've always felt this way... enjoying a story is more about the experience the writer creates while telling it. I always encourage people to go ahead and "spoil" the story for me.
Because often times you don't remember the domain exactly & then you've got the same problem. Anyone remember whitehouse.com or countless other examples of this? The fact that Google is probably 99%+ effective at getting you where you want to go heavily disincentivizes relying on your brain which may not have as high a success rate as Google. Plus all the browsers have gone in this direction since search terms are more usable than domain names.
Of course. This could have happened to any site, but in this case I just found it funny because 'JQuery -> jquery.com' is so simple and obvious. I'm sure the author knew the actual domain, but used google out of habit or preference.
Signing up for anything google feels more like a commitment compared to creating a twitter account. Google wants to integrate more and more of your data into their system, linking it with your other google accounts whether you like it or not. G+ seems, like FB, more like an experience than a simple service. Not that it cant provide the same function as twitter, but providing only that function is still valuable, I think.
Now that the hype is dying down, maybe people will start thinking more about how to make bitcoin easier and more available and less about how they can profit off of mining and trading.
Start? People have been thinking (and working) on that even before the hype began (see for example the Android client now on the frontpage, or the new client UI being developed, wallet encryption being tested now, and various web payment services), it just gets drowned in all the trolling, mining related talk and price speculation.
Wow, awesome. It shouldn't be hard to create a binding for execvp as well then. I found the pipe() binding, but I can't use those fd's with child_process.spawn if i want to open them as fd 3, 4, 5, etc in the child.
child_process.exec is different from n*x system exec. Node is still doing the fork()ing and exec()ing behind the scenes. Exposing those calls in node would give you direct access to the child process before executing your commands.
Because they aren't trying to sell a product. This is an announcement directed towards developers and coders using node who wish to contribute by trying out new features. Calling it 'unstable' makes it clear what it is and what it isn't.