heroic

A lot of your article goes on to talk about development time speed up. The original article discussed performance where it is critical, like a game. You can't have compensate on performance even if it comes at the price of higher development time.

I guess because it's not twitter!

I and a colleague used Knapsack algorithm for a very interesting use case. You can find it here https://github.com/heroic/Rucksack

it makes for a great stress buster, imo

how is adding things like caches adding a CDN?

This is what internet should look like again!

Beats this! http://www.hmv-news.co.uk/register.php

LOL, i entered my handle and it says I am not my handle!

What I dont get is, how is a software scanning my email creepy? As it everyone scans every bloody email to seek out spam. Spam filters already use "known" spam styles to check for potential spam messages.

In this case they are scanning to show you ads. Pardon me if I am missing something, but I really don't understand wtf is wrong with people calling this creepy.

Use this : http://wiki.nginx.org/HttpLimitReqModule

Thanks!

Hey! you can buy a toll free number, or a number in different countries for your users.

Firefox on mac shows me this :P

https://dl.dropbox.com/u/14534468/Screen%20Shot%202012-09-10...

The 1 instead of ! in the title

actually, you can not predict crimes of passion, but planned crimes, well, you definitely can, cant you?

this reminds me of person of interest

yes i am! the post wasn't done by me though, so "they"

just curious, what browser and on what OS are you using? I was able to see the action they say...

that is only for olark, this is more of a framework. You get to choose the action you want to take.

It is because Java is like PHP. it is synchronous. If your app is doing a lot of non-cpu stuff, it makes complete sense to use an async programming model.

The reason it is advised to not load static files via Node.js is that nodejs is a single thread process, and static files will hold up this thread. Nginx on the other hand, is multithreaded, and can continue serving other assets and requests while the statics are being served.

you can simply check for the accepts header.

Another tip for people using express is to not use middleware that is not needed in every request. You can specify special middleware for every path. So you can even split session usage only on pages that need it. Similarily, cookie parsing, etc can be avoided where not needed.

A very fine way is to have multiple processes and connect to any at random. Now, use a message queue, say like redis, or rabbit mq to read messages and delete from queue. Since a client is only connected to only one of the servers, it eliminates the chances of sending the same message more than once to the same client. This helps in splitting the incoming messages and the outgoing(which is usually far bigger, since one message is delivered to all others in a chat room).

What java service?

IMO, things like a good ORM(or ODM) are still way too far off in NodeJS. I am aware of mogooseJS, but it is very far from the power provided by ActiveRecord and Mongoid.

Also mocha is powerful, but if you have a look at capybara and rspec, they are much more powerful and friendly.

The final thing in my opinion is the speed of development. With rails you go to devise, and you have authentication. I am aware of the presence of a similar authentication system for nodeJS but I am not very sure if that works with mongoose js and is as extensible as devise is. And then there is the rails console, which makes trying out things real easy and fun.

Actually since the app was developed at startup weekend which gives you 54 hours to make a presentable demo, I'd say testing was not the first thing on their mind.

There is a project coming up - railwayjs. I hope it changes the way people use nodejs!

"Node.js is a platform built on Chrome's JavaScript runtime for easily building fast, scalable network applications."

From nodejs.org

First thing is that NodeJS is not a JS engine, V8 is. Second, http://notinventedhe.re/on/2011-7-26. That is from http://nodejs.org/community/ which makes the terms quite right, i'd say.