node.js

var http = require('http');
http.createServer(function (req, res) {
    res.writeHead(200, {'Content-Type': 'text/plain'});
    res.end('GRUNNUR\n');
}).listen(80, "'0.0.0.0');


What do you think prog? It's kind of like twisted for python, except the whole language is designed around the event loop and non blocking I/O.

http://nodejs.org/

what do you think /prog/?

sure, looks good if you need to do something that twisted or eventmachine does. what do you want us to discus, OP?

>>1

require();
createServer().listen();


I have a theory:

``The easier it is to create/listen to sockets in a given programming/scripting language, the shittier the aforementioned programming/scripting language is.''
    --Xarnonymous

>>3
u mad no one wants to join your elitist masochist club?
Though I do agree that everyone should be able to handle sockets in C.

>>4
everyone should be able to handle sockets in C
You mean, BSD Sockets? Windows Sockets? Boost.Asio?

Thing is, neither C nor C++ have a standardized Sockets Interface. And even if you use BSD Sockets, which are widely usable on Windows, you will still get different results, due to lack of standardized interfaces.

Enjoy your tons of #ifdef's

#ifdef's
Faggot.

^___You are all ``faggot''s.^___

>>5
Don't hate me, I just want to fit in :(
I've only really written Windows C code, so I used Winsock.

>>2
OP here. I was looking for /prog/'s professional opinion on javascript as an event-driven server-side language

>>8
Windows sockets are hardly different from the standard unix sockets, the only major difference is the init/uninit code.