At 1000+ karma, you take off your helmet and guess what you're a chick. If you win three times in a row on impossible mode with perfect karma without getting shot once, using nothing but the annoying gun that takes forever, you take off your armor and guess what you're a hot chick. Then you can play the game again wearing a bikini.

At 2000+ karma, Paul Graham comes to your house, tells you the meaning of life, and makes you a sandwich. It is the best sandwich known to man. Only rich people can make this sandwich.

6 more points to go!

*Thanks to everyone who voted this up. I can now confirm that this is indeed legit. On your settings page you can enter a six digit hexadecimal number that will change the color of the top bar. I'm going to try some of these out! http://www.somacon.com/cgi/colorchart.pl

I don't care about algorithms, binary trees or what fuck. I can code a web page in a day and that pays the bills.

It could have been an echo, a print or a put, but it had to be simple for us, not scary as system.console.writeln()

Most of you will never understand, you all come from a C or Lisp background and can make a computer cry for sure. We don't care, we just want to spit HTML in shiny ways and 'echo' is all we need.

As the author hopes we forget about his post before he has to write about why it matters. They're both good frameworks. Rails has more books for a number of reasons:

* It's been around longer. It also achieved API stability sooner. Not that Django had an unstable API, but there were big changes for longer (such as newforms). So, Rails has lent itself to having books written about it for a lot longer and has gone through many revisions since the books started coming out.

* Django has better documentation. Sure, Rails has its guides section and api-doc, but Django's documentation tends to be better than multiple books. So, there's been less of a push for books. Also, with Adrian and Jacob (the co BDFL of Django) having put a free book out there at djangobook.com, it means dead-tree books are likely to make less money.

* The Django community is smaller. Smaller means less people buying books, means less books written.

This post is the ultimate in link-bait. What's next: Why Java is better than Lisp: curly braces! I'll write more on that later ;-)

That's not a jab at Microsoft. I was just thinking there must be something there with respect to employee benefits, or maybe just employee treatment, that other large companies may want to look at.

Out of curiosity, are there any ex-MSFT employees here that could tell us what you like or dislike about MSFT? I guess the most illustrative ideas might come from knowing what you MISSED when you left MSFT. If anything.

Turns out they rely on the "but we're GOOGLE!" schtick a lot when hiring.