Comments on: ServerSide JavaScript with MooTools and NodeJS

By: Vic

Vic — Fri, 02 Sep 2011 20:53:51 +0000

exports = MyClass = new Class({
works, is that right?

By: Chris the Developer

Chris the Developer — Tue, 31 Aug 2010 09:37:51 +0000

var User = require(‘User’); should be var User = require(‘User’).User;

By: Nick Tulett

Nick Tulett — Sat, 24 Jul 2010 07:07:07 +0000

If you can’t quite grasp the significance of node.js, then re-read this:

“This is the main design goal of NodeJS: to be non-blocking for any I/O operations such as reading or writing a file, storing or retrieving data from a database etc.”

It’s not a semantic replacement for PHP and it’s not something you run on top of a webserver, it’s something you use to build a different kind of fast, scaleable web application.

By: Marco Rogers

Marco Rogers — Tue, 13 Jul 2010 14:31:04 +0000

“If extending the native types in JavaScript does not align with your style of coding you should probably not use MooTools (or JavaScript, as it is a core feature of the language).”

Really? I know you guys are opinionated about this type of thing, but sheesh. Anything you can enable by extending base datatypes, you can also do without using that “feature”. And as soon as you load two modules that presume to know what’s best for your base datatypes without telling you, you’re probably going to run into unintended behavior.

Sorry to be off topic. This is pretty awesome work. That unnecessary comment just caught my eye.

By: doertedev

doertedev — Tue, 13 Jul 2010 06:50:04 +0000

Good article m8.
Somehow NodeJS really rocks. nearly every webdev nowadays knows JS and therefore can write pretty neat stuff on his system layer that runs like hell.

But what about this: What the hell do you need it for? What does NodeJS do better on the lower areas that won´t be a bit more achieveable with PHP / Python? I´m not flaming like “omg php > js” but I think for most of the stuff I need the compiler. NodeJS is hot but why do ppl actually ask for apache & php integration? Because they are familiar with it and they do know what they actually do (more or less… more less then more :P).

I couldn´t find a well suited case for using nodejs yet. And yes you can rebuild apache with nodeJs. Would you whant to? Would you really whant to go through all this security stuff that the apache guys been dealing with for years? Have fun with it, you have my full support but get a life ^^

By: Alex

Alex — Tue, 13 Jul 2010 02:21:56 +0000

An awesome extensive article about something really interesting.
If someday I’ll need a javascript server, it will definitely be set up with Mootools and Node!

By: Dan

Dan — Mon, 12 Jul 2010 16:07:15 +0000

From an SEO perspective JS output from server side would presumably appear in the source instead of the script and so would be a real win.

By: Christoph Pojer

Christoph Pojer — Mon, 12 Jul 2010 15:24:15 +0000

Jaxer is dead.

If you want to run javascript on apache have a look at v8cgi ( http://code.google.com/p/v8cgi/ ). mootools-loader should work with v8cgi even though I have not explicitely tested it.

NodeJS is not an apache module but basically an application that allows you to run javascript code on the server, with asynchronous access to resources. You can – as seen on http://nodejs.org – build an apache like webserver with nodejs.

By: Tim Wright

Tim Wright — Mon, 12 Jul 2010 15:13:50 +0000

Any reason you chose NodeJS over the Apache Module Jaxer? Will Node run on Apache?

By: Rohit

Rohit — Mon, 12 Jul 2010 15:05:30 +0000

Certainly is interesting. But still speculating, whether a JS server side is of any use, or is a web language still better there. Well, to each one his own !