Node.cs - a C# version of Node.js

by jitbit • 14 years ago

86 26 14 years ago

Is this still in active development? Looks like it hasn't gotten much attention in about a year or so. Wonder if the project has moved somewhere.

mxweas• 14 years ago

holy god no...

adestefan• 14 years ago

I say the same thing about writing backend code in JavaScript.

theon144• 14 years ago

Why? (Honest question, I don't know much about JavaScript or backend development)

omgtehlion• 14 years ago

I suppose that main point in node.js is asynchronous execution, and in c# we already have all these features. I actually can’t see a point of this library in production app.

zedr• 14 years ago

Not only that, but one of the main selling points of Node.js is using one language (JavaScript) for both client and server programming: the holy grail of Web application development.

AntiRush• 14 years ago

There are various C# solutions for frontend web development.

SharpKit[1] is probably the most mature.

[1] http://sharpkit.net/

pjmlp• 14 years ago

Yeah, for the developers that have a brain small enough to handle multiple programming languages.

thepumpkin19792• 14 years ago

I thought it was because Javascript didn't have a Threading model... that Javascript is also used in the Browser is just a coincidence I think.

dos1• 14 years ago

Node.js is becoming a first class citizen on Windows, so I'm not entirely sure what the point of this is. IISNode even allows you to host your Node.js apps in IIS.

If you're desperate for some kind of evented web framework in C#, check out SignalR - https://github.com/SignalR/SignalR

plasma• 14 years ago

I recently came across SignalR, it's a very well written and simple framework to use.

The buzzwords are web sockets, comet, ajax push, etc.

barrydahlberg2• 14 years ago

Being able to write C# instead of JS is a pretty big point IMHO.

lwat2• 14 years ago

What do you gain in using this that you could not already do (better) on .net?

hinathan• 14 years ago

While we're at it, I'll throw in my demo of node.js style closures triggered by events on I/O with PHP and libevent: https://github.com/hinathan/edges-php

MarkSweep• 14 years ago

The new await keyword in C# can be used to write coroutines libraries like this, but instead of you writing the continuations yourself, you can let the compiler slice up your function. You can then leverage the SynchronizationContext class to control which thread the continuations run on.

Looking at the use of libtask in mongrel2 inspired me to play around with the idea of coroutines in C#. The await keyword makes my latest iteration quite small and nice to use. https://github.com/AustinWise/LibTaskNet

aaronblohowiak• 14 years ago

you can also do this in luvit (libuv + lua)

petercooper• 14 years ago

Similar in C++11: https://github.com/d5/node.native

And a simple example of using it (for a hello world benchmark): http://www.devthought.com/2012/02/08/node-http-hello-world-s...

johns• 14 years ago

A more serious attempt at this was Manos de Mono which has also since been abandoned. With Node getting a lot of love from MS there's little need for a clone.

https://github.com/jacksonh/manos

equark• 14 years ago

Adopting Node's callback style seems like a very strange choice for C# where you have native async/await support.

Node.cs - a C# version of Node.js

Related Stories