11–20 of 22 posts
It was discussed a while back on HN: http://news.ycombinator.com/item?id=1477084
This source is on GitHub here: http://github.com/mape/node-wargames
Also, Node Knockout (http://nodeknockout.com/, a 'build a node app in 48 hours' competition) is happening at the end of August, and I expect some cool stuff to come out of that.
In fact, what would be a use case of Node.js? I know it is a rather interesting tech but other than that what do you/would you use Node.js for?
- You get to write JavaScript on your back-end and your front-end.
- It's evented (like Twisted, EventMachine, etc) which has proven popular/robust/fast recently (think FriendFeed).
- It handles insane amounts of requests/second (due to non-blocking IO and V8 awesomeness among other things).
- Did I mention you get to write more JavaScript? :)
- It makes it pretty easy to implement servers for other protocols than just straight vanilla http -- for example WebSockets implementations and so on.
Here's an offline-capable web application and underlying "network-straddling" framework running on Node: https://szpil.com Node is great for handling many concurrent clients. It extends the V8 interpreter with excellent low-level APIs: Posix, Tcp, Http, DNS. If you need to share Javascript code between client and server, Node is the best server-side Javascript environment you could choose to use.
In fact, what would be a use case of Node.js? I know it is a rather interesting tech but other than that what do you/would you use Node.js for?
GitHub uses it for their download links to get an archive of a repository. There's a blog post about it somewhere.
Here's a little Node.js/CoffeeScript application I worked on for a contest at a conference: Site: http://apiplayground.org Source: http://github.com/jashkenas/api-playground/blob/master/src/a... The source is interesting because it demonstrates something that you can't do easily with a regular Rails/Django app: nonblocking asynchronous calls to remote APIs, with synchronous responses to the ajax request.
Here's an offline-capable web application and underlying "network-straddling" framework running on Node: https://szpil.com Node is great for handling many concurrent clients. It extends the V8 interpreter with excellent low-level APIs: Posix, Tcp, Http, DNS. If you need to share Javascript code between client and server, Node is the best server-side Javascript environment you could choose to use.
What about ffi access? Could I load libmysql.so and use javascript wrapper around its functions or it must be implemented 'in pure Javascript'? ^_^