Interesting for construct / pluginmakers ?

http://nodejs.org/

The problem with node.js, is that you need to run it as a server. Since webbrowsers are considered as client only (for security reasons), you need to find a way to provide an executable version of the nodejs binary to your user.

On FF, you can use something like POW (an extension plugging a webserver inside FF), on Opera, there's Unite, which has his own limitations, but I don't think there are something available natively for the other browsers...

I think that plugging into other frameworks would be great. I was just thinking this morning on how I could start to think about isometric MMO's using Scirra and Isogenic Engine. Looking at the upcoming future of development I am also thinking about LAN play and an article here:

rawkes.com/blog/2011/12/05/running-node.js-from-within-a-firefox-xul-extension

So node.js would be an interesting integration along with some multiplayer features.

From Pode, browser can not be a server without any addition. So we still need do something to create a server.

I had made a Chat plugin by using socket.io client. The server is using tronadio2, a python module, and pack into a stand-alone execution program.

Node.js would be great for an online multiplayer/websockets plugin, since you can write both the server and client side in javascript.

And while you are at node.js, throw mongodb in as well!

Mipey,

did you do something to your avatar? it's not as sharp as i remember it being. kinda fuzzed out now.

Ah, the original size is 83x80, seems it doesn't look as good upscaled. Doesn't bother me that much.

I try to install Node.js in a stand-alone execution program in window7, but fail.

For now, it does not have an easy way to install node.js in windows.

this seems to work , but i guess you cant call it easy..

Apparently node.js is cancer

Mipey, that post reads like a load of nonsense to me. Node.js is non-blocking for I/O. That guy rants about how it blocks for the CPU (obviously it has to). The CPU is not I/O, so they're arguing about something different to what Node.js is for :P They also complain that you have to use javascript, which is also another big advantage, since you can share code between the browser and server...

I think the tl;dr sum up everything : that guy doesn't like it...

I thought it was strange that someone would set up a blog for node.js bashing specifically...