I want to state some points that should be obvious: - All three techonogies mentioned so far (Django, .NET and Rails) can work on flawlessly on big, important projects when used correctly, or can fail on medium/small deployments when used incorrectly.
- .NET is a lower-level layer than Django or Rails, it's more comparable to Python, Ruby, or (more so) to Java. But, being a single-sourced technology, the framework on top is more 'obvious'. also, since most of the infrastructure associated with .NET comes from Redmond, the evolution paths are clearly defined, just like it used to be with Java, where 'a web using Java' was almost always J2EE. - Any framework scales just up to a point, and then you have to start replacing some generic parts with custom implementations that work best for your specific problem. just how long can you stretch each before you see the voids and start filling them depends somewhat on the framework itself, but much more on the skill and experience of the developers. - taking a group that's experienced and productive developing with a framework and telling them that you want them to use another one that they're not familiar with is a sure path to failure. not only because of lack of experience, but also because they might not want it to succeed, and they even have a clear excuse. in fact, failing at it makes them look better because they were suggesting the other way from the start! just don't do it. -- Javier -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
