Study compares productivity levels of Python+Django vs. C#+ASP.NET
Posted Thu, 25/02/2010 - 13:34 by udib
A recent study measured the productivity of using Python+Django vs. C#+ASP.NET, in terms of user-stories per week. The results are that 1 Django developer is equivalent to 2 ASP.NET developers, productivity-wise:
http://kurtgrandis.com/blog/2010/02/24/python-django-vs-c-asp-net-produc...
The Django team that participated in the benchmark, BTW, had no prior experience with Django, which probably implies that the difference can be even higher.
Comments
& BTW, comparison with Java should be not that different, as at least in verbosity, C# & Java are similar (C# perhaps less verbose). Just saw this code comparison between Java & Python:
http://gist.github.com/313924
1 line of Python ~= 35 lines of Java...
Not that I am in favor of any programming language, however such comparisons such as the one devised by the link you provided is exceedingly prejudiced.
First, Django and Java are from top to bottom dissimilar, how can you even compare between the two when one is a very mature OO language while the other is an interpreted scripting language?
Second, when a java programmer is using the readUTF method , he doesn’t have to write “50” lines of code (which is a wrong impression that can be inferred from reading the post), rather, he also writes a single line of code:
InputStream inFromServer = client.getInputStream();DataInputStream in = new DataInputStream(inFromServer);
System.out.println("Server says " + in.readUTF());
Its true that Python is more fruitful (http://pythonconquerstheuniverse.wordpress.com/category/java-and-python/) with respect of lines of code and that this “advantage” is proliferated by the capacity to run code right away without an a priori compilation step. However, In terms of agility, the Java engine does offer the option of running JVM bytecode generated by different languages, not only Java and that is a large benefit not available on the python side.
I agree. Also:
1. With languages like Scala and Fantom lines of code are significantly reduced.
2. Lift 2.0, for example, offers a development cycle that is close to the RoR one.
3. Today, the Java community understands the need for a more productive development environment and works hard to get it.
So, while the JVM and JVM languages preset a promising future in which productivity gaps will be minimized (or, hopefully, won't exist) without sacrificing performance/security/stability/etc. , Django doesn't.