The terms rapid web development gets associated with Python/Django and ROR. Why is this not the case with C# ASP.NET?
3
-
2Source or it doesn't happen.– Steven EversCommented Jan 5, 2011 at 16:15
-
3SnOrfus is correct, you need to specify your source or provide us some published data to back up your statment.– WalterCommented Jan 5, 2011 at 16:28
-
Its just the impression I get browsing the internet. Every new startup that utilises agile developement and rapid prototyping methodologies seem to be using ROR or Pthon/Django– NaiCommented Jan 5, 2011 at 17:32
Add a comment
|
3 Answers
There is no such thing as a "rapid development framework" or "rapid development language". Any framework, language, or toolset is equally possible for use in a rapid development environment as any other.
Rapid development has nothing to do with languages or technologies used. Rapid development is a methodology that favors producing prototypes frequently with minimal up-front design and planning.
answered Jan 5, 2011 at 16:23
-
What languages/frameworks are best suited for rapid web development methodology then?– NaiCommented Jan 5, 2011 at 16:29
-
1None. It's a methodology that is independent of all languages, frameworks, and tools.– Thomas Owens ♦Commented Jan 5, 2011 at 16:30
-
2That is a bold statement that technologies and languages don't impact developer productivity. So why have we bothered inventing new frameworks and languages over the past several decades? You are saying that I could develop as quick a web application using ASP.NET or RoR as I could with C++ or Perl through CGI? Commented Jan 5, 2011 at 18:54
-
@jkohlhepp This isn't about developer productivity at all. It's about adhering to a specific process or methodology. You can choose to follow the principles of RAD with any language and saying that one language makes following RAD easier is just wrong.– Thomas Owens ♦Commented Jan 6, 2011 at 3:57
-
1@Thomas I guess I just plain disagree. Forgetting the "RAD" buzzword, some frameworks and languages make things quicker to develop than others. That seemed to me to be what Nai was asking about. Commented Jan 10, 2011 at 14:36
ASP.NET when developed as an application requires that you compile the project into a dll; it is possible sometimes to make simple changes to the .aspx files and get immediate results but it is not as dynamic as other platforms.
-
This is a minimal difference. It is an extra 5 seconds when hitting Run before you see the app. Commented Jan 5, 2011 at 16:18
-
1Not really when you have an app with hundreds of pages and classes. Commented Jan 5, 2011 at 16:19
-
2Not sure what settings you are using, VS will only compile what it needs to. Unless you are forcing a re build every time. I'm modifying code while debugging and the changes are happening fine. And some of the projects very very large indeed. Commented Jan 5, 2011 at 16:39
I have done a lot of development work with ASP.NET. I don't know much about Python/Django but I have done some reading on Ruby on Rails. I think the main reason that RoR is considered more RAD than ASP.NET is scaffolding. ASP.NET does have some scaffolding features (and ASP.NET MVC has even more), but I think RoR's is generally more powerful. Also, ASP.NET developers in my experience tend not to use the scaffolding features even when they are available. And the scaffolding features in vanilla ASP.NET tend to lead you down bad architecture and design paths, whereas the scaffolding in RoR tends to lead you down the correct A&D path.
In reality, ASP.NET can be a pretty rapid platform. For any non-trivial web application, I think the differences between RoR and ASP.NET would be minimal, especially if the developers are proficient in whichever platform.
answered Jan 5, 2011 at 16:17
