What are the downsides of using Django compared to (ASP.net MVC, NHibernate, and Spark View Engine)?

Question

I'm new to ASP.net MVC, but I'm pretty used to Django. I find ASP.net very pulling to do even small things. When comparing Django with ASP.net MVC with NHibernate and Spark View Engine, am I missing something in Django, what makes ASP.net too good? Is ASP.net performance much better than Django since compiling ASP.net?

Answer 1

If you are new to ASP.NET MVC but are happy with Django, and you want to evaluate ASP.NET MVC only in essence, then this could be a clouding of your assessment by adding another new technology, for example, the Spark View Engine . Something worth trying, use the NDjango View Engine instead , so you can use the same view syntax you are used to, and then just look at ASP.NET MVC as a technology.

If you find that ASP.NET MVC is slowing down or bothering you, but still wants to work with .NET, you can always give something like NancyFx an attempt that has simplicity built into its core (taking some design cues from popular Ruby Sinatra framework ) and also supports both Spark and NDjango.

, , Python , Ruby, , , ( ) , . , , , .

, Rob

: Spark View Engine, , , . , , , Spark - , : -P

Answer 2

: http://drozdyuk.blogspot.com/2009/03/django-and-aspnet-mvc.html

blogpost ASP.NET MVC .

, , /? , , Apache, .. / Django, ASP.NET MVC .