randylahey

Could you elaborate? Joyent has been offering a production-ready (not beta) container cloud for for years.

I wonder what reasons there are for not putting npm in a foundation in the same way that happened to Node itself? Surely such a critical piece of Node infrastructure shouldn't be controlled by a single (for-profit) company.

What are you getting at?

I'm no Sports-Ball expert, but two things you can do to make Football more enjoyable is lose the padding and lessen the constant pauses of the game (which frustrate me to no end, as a casual observer). These two reasons are why I find Rugby infinitely more enjoyable to watch.

I look forward to the day I can teach my kids to use Vim :)

Vim is still free.

Sure, everyone has to start somewhere, and to be perfectly honest, I ran into many of the same issues.

The difference is in what happened afterward. What I did then was to try to understand why Node.js did things differently and how I could accomplish my goals in an idiomatic way. I didn't try to shoe-horn in my existing mental framework for how things should work, and then throw my hands in the air when they didn't.

However, what I didn't do was immediately run to Alert the Internets about what "A Giant Step Backward" Node.js is.

Nitpick: Incorrect. Node.js uses a thread-pool to run things which are necessarily blocking, such as some POSIX functions.

It's kind of a dick move to make a inflammatory, flamebait blog post and then later admit you didn't actually know what you were talking about. Maybe you should have actually understood the technology you were working with before making knee-jerk snap judgements.

Doesn't that seem reactionary and knee jerk? Do you not use countless other products because their names have been trademarked by an organization?

Node.js is MIT licensed, so no, that won't happen.

I wouldn't say based on, it actually takes place in the city.

I wish this was rated higher. I don't understand the fuss about "spaghetti code". Do all those people write spaghetti code in other languages? Because I see that not as a language failing but as sloppy programming.

What's so hard about this to get a sequential execution of functions/blocks, error'ing out on the first error:

    async.waterfall(
      [ function (callback) {
          // do thing 1
          callback();
        }
      , function (callback) {
          // do thing 2
          callback();
        }
      , function (callback) {
          // do thing 3
          callback();
        }
      ]
      , function (error) {
          if (error) {
            // ohnoes errors
          }

          // all done!
        }
      );

Maybe they should take the hint and move the fuck away from elephant country? Nah, easier just to kill them.

Right, because no one should be worried when Apple makes overtures towards monetizing what has been traditionally the only working compiler tool chain for OSX. Thanks, I guess I was just over-reacting. :P

It's amusing how any time Apple does something like this the apologists come out of the woodwork falling over each other to defend them.

The point is not that it's $4, or $10,000 or $0.25. The point is that now that money has to come from somewhere. This throws up a sizeable obstacle for anyone looking to do development on the platform and will especially hurt FOSS.

If you can't see this, I don't really know what to say. Apple literally makes billions of dollars on software, you'd think they'd throw the developers that literally helped build their ecosystem a freaking bone. I suppose that's too much to ask from Apple.

Cue the "vote with your wallet", "no one is forcing you to use it" rabble...

Apples will never replace oranges.

Holy FUD! I'm sure all the Lisp and TCL fanboys thought the same of their supposedly superior runtimes all the way to eventual irrelevance.

Hubris much?

I would hardly call window.prompt and document.write i/o since they never hit disk or network (to over-simplify). They're more like manipulating an object in memory.

For real i/o in JavaScript, look at AJAX: Callback based.

That completely defeats the point of using Node.js; that is, to use an evented model so your app isn't sitting around waiting for IO. s-node wouldn't be node at all.

FWIW any other runtime/framework will do what you suggest. For example, Rhino.

Why is it okay to do bad things if others do it too?

1. The title is not untrue.

2. It's not known whether this will lead to a full blown "conflict" (although, who are we kidding, it probably will)

Uh, you mean like China?

I realized I had lost an important file (a letter of recommendation from my university co-op placement). I no longer had the e-mail it was attached to (this is prior to me using webmail), nor the e-mail program. But what's this? I still have the mailbox files. Well, I know python has some multipart utilities... maybe I can copy and paste the relevant parts out of this message and into a script and have it write out the attachment sub-message. After a bit of fiddling, it worked!

I was elated. It was by no means a very challenging thing to do, but I would have been totally fucked if I didn't know how to do software development.

Who's suing whom.