Django vs. Rails: The Dead-Tree Edition
1–10 of 37 posts
Re: Django vs. Rails: The Dead-Tree Edition
#2Re: Django vs. Rails: The Dead-Tree Edition
#3I don't understand, why does it matter?
Re: Django vs. Rails: The Dead-Tree Edition
#4I don't understand, why does it matter?
If it did matter, what would we learn by comparing .NET books w/ Rails books, or Seaside books with Django books. Surely the number of books isn't the point.
Re: Django vs. Rails: The Dead-Tree Edition
#5Re: Django vs. Rails: The Dead-Tree Edition
#6Jesus books (333,560): http://www.amazon.com/s/qid=1232312844/ref=sr_nr_i_0?ie=UTF8...
Rails books (428): http://www.amazon.com/s/ref=nb_ss_b?url=search-alias%3Dstrip...
Re: Django vs. Rails: The Dead-Tree Edition
#7http://i44.tinypic.com/98uhs6.png
Now it looks like they turned into Java?
Re: Django vs. Rails: The Dead-Tree Edition
#8Re: Django vs. Rails: The Dead-Tree Edition
#9Is it because Rails is popular and emits a lot more noise than Django? Yeah, probably.
Re: Django vs. Rails: The Dead-Tree Edition
#10I don't understand, why does it matter?
I’ll write about why this matters tomorrow.
Tune in tomorrow!
All I can figure is that either (a) Java and/or PHP are about to declare "victory" again, whatever that means, or (b) it will be concluded that the framework with the smallest number of books is superior because the docs are DRYer than everybody else's docs. Which might well be another moral victory for some obscure Lisp dialect.
I'm holding out for option (c): A collectible card game in which teams of software books are assembled to fight holy wars against each other. SICP, I choose you!