4 ms·
> Django for Python is largely a rails clone Django was initially released in July 2005 (https://en.wikipedia.org/wiki/Django_(web_framework) https://en.wikipe
by jacinda 11y ago
> Django for Python is largely a rails clone
Django was initially released in July 2005 (https://en.wikipedia.org/wiki/Django_(web_framework) https://en.wikipedia.org/wiki/Django_(web_framework)).
Rails was initially released in December 2005 (https://en.wikipedia.org/wiki/Ruby_on_Rails https://en.wikipedia.org/wiki/Ruby_on_Rails).
Just a minor quibble. They basically grew in parallel and implemented similar feature sets, but the timing hardly allows for cloning.
- astrodust 11y agoCakePHP is a clone, or at least so heavily inspired by it may as well be. Django does its own thing, and while it has borrowed ideas, it is an entirely different beast.
- jacinda 11y agoAgreed.
- anjc 11y agoDoes anybody know which framework they were both inspired by at the time? I'd guess that the concept of MVC has been around for a long time but what kicked off the popularity in 2005? CakePHP was released before both of them, in 2005 too.
- chc 11y agoCake was released first, but I'm not sure that it looked much like later Cake did. It's been too long to remember.
- mooreds 11y agoBacklash against Struts and other java MVC frameworks that were configuration heavy?
- troels 11y agoRails at least, was heavily inspired by the book Patterns of Enterprise Application Architecture from 2003. That - in turn - drew a lot from the Java world, that was the lingua franca at the time.
- anjc 11y agoAh now that's interesting. Thanks
- jamie_ca 11y agoI don't know the pre-1.0 history for Django, but I started with rails 0.7, and 0.8 was [released](https://rubygems.org/gems/rails/versions https://rubygems.org/gems/rails/versions) October 2004, with much of the core architecture in place.
- vonmoltke 11y agoDjango was released to the world in July 2005, but the developers started it as an internal project at a newspaper in Lawrence, KS in late 2003.
- dguaraglia 11y agoAlso, they have (or had, at the time) completely different philosophies: while Rails was highly tied to "convention over configuration", Django went the other way after the "magic removal" branch and it became fully "configuration over convention". When I had to chose one over the other, I ended up using Django simply because diagnosing issues was simpler. Rails required a pretty substantial amount of a-priory knowledge to get things started (think, naming a file or method a certain way for it to magically be available somewhere else.) Django was more straightforward and allowed you to write code that, while not 100% django-esque, would work. I remember doing a lot of refactoring whenever I'd figure out a new framework idiom that I had missed earlier, but hey... I had working code before I needed to learn the idiom.
- verisimilidude 11y agoRails was around before December 2005; that was just the release date for version 1.0. I know I had a personal site running on pre-1.0 Rails in early 2005. But your general point stands, Rails and Django grew up together and cribbed from each other liberally. The biggest example would perhaps be the merging of Merb into Rails 3, where Merb was a competing Ruby framework that had a much more Django-like vibe. These fanboy arguments don't hold much weight these days. They each do their own thing, they each borrow the best from each other, and everyone benefits.