Unfortunately, even comparing them is useless. Each is used in their respective industries. When is the last time you heard of an all web start up delivered from ASP.Net? I'm sure there are exceptions, but its to a rule.
Ruby on Rails is easy to patch yourself, it has a low buy-in, and it is cross platform. .Net MVC is giving medium businesses and enterprise web portals a much needed face-lift.
What I don't see a lot of, is stories of one cannibalizing the other or competing solutions. You don't see many headlines "Startup chose ASP.Net, it made all the difference"
Agreed. Interesting to see the trends though, considering ror 3 went golden a few weeks ago. (Btw, I use both aspnet mvc and ror depending on client requirements).
I suspect the "trend", such as it is, is entirely meaningless. When Ruby on Rails was new and unfamiliar, people tended to google its full, cumbersome name.
Now, people tend to just shorten it to "Rails", and indeed the top three hits for that are Ruby on Rails sites.
Ruby on Rails is an open source framework built using an open source language that runs (primarily) on an open source stack.
ASP.NET MVC is an open source (used loosely [MS-PL]) framework built on a proprietary framework, using a proprietary language that runs on a proprietary stack.
In my experience, there hasn't been a lot of cross shopping of these two technologies. A developer who gravitates towards RoR is far more likely to look at a Python framework than ASP.NET MVC. Likewise, an ASP.NET developer is more likely to cross shop something like Java; pick a framework, any framework.
> an ASP.NET developer is more likely to cross shop something like Java; pick a framework, any framework.
In my opinion, an ASP.NET developer is more likely to cross shop with whatever next technology is marketed by MS or whatever the company they have been working for decides to switch to (be it Java or whatever).
A Ruby, Python, PHP [Name your OSS language/platform] developer is much more likely to switch to Java (maybe not the language, but the platform) than any .Net developer ever would be.
When I started to use RoR around 2006 it was quite difficult to find good documentation. So you had to use Google quite a lot to find something useful. Nowadays RoR is better documented and you can find everything you want to know in a few central places. So people may have to search less to find what they want.
Adding python as a keyword probably lowers it a little too much, but at least it starts in 2005 when Django was released and is smaller than rails (I am a python fan, but I doubt django is bigger than rails).
Is there a way to filter out east Asia? there's a lot of people there. Either way, the graphic does not really show a great increase for the dot-Net framework but a bigger decline in searches for RoR.
You can see that search volume growth for "rails" had been flat for the year before Ruby on Rails came out. Since then, "rails" trended the same as "ruby on rails" at every point in the last six years. Right now, the search volume for "rails" is still trending 10 points higher on the graph than it did before RoR came out; to put that into perspective, searches for the full name "Ruby on Rails" have been less than 10 points since the start of 2008. All this indicates is that people have learned they can get good results by typing "rails" instead of the full name.
I want to add that it's possible that nearly all correlation between "rails" and "ruby on rails" is due to the possibility that google double-counts "ruby on rails" searches as "rails" since that word appears in the full name. However, the 10 point increase in "rails" still trends 5 points higher than the 5 point increase in "ruby on rails" during the same period of first release in 2005 to now in 2010, which is double. But anyway, the point isn't that my stats are any better; the point is to demonstrate that it's hard to make an inference based on two keywords, and even harder to predict what will happen based on this information, even if it was accurate.
No news here except that there are many MVC web frameworks these days.
25 comments
[ 2.9 ms ] story [ 67.2 ms ] threadRuby on Rails is easy to patch yourself, it has a low buy-in, and it is cross platform. .Net MVC is giving medium businesses and enterprise web portals a much needed face-lift.
What I don't see a lot of, is stories of one cannibalizing the other or competing solutions. You don't see many headlines "Startup chose ASP.Net, it made all the difference"
Now, people tend to just shorten it to "Rails", and indeed the top three hits for that are Ruby on Rails sites.
There's no meaning to be found in this chart.
Mind that ruby rails probably includes searches for "ruby on rails".
Sadly, clean trends for "rails" are not really meaningful - mass transit seems to be most popular of these all.
Rails people don't search "ruby on rails authentication" they search "rails authentication."
My guess is that Django and asp.net mvc people search for "django authentication."
(My assumption is that google counts a search for "django auth" as a search for Django in trends.)
This means that as Rails grows in popularity, "ruby on rails" will decline, since many many developers now know what it is.
* However, as Django and others grow in popularity they hang onto all the people searching for "django xyz"
ASP.NET MVC is an open source (used loosely [MS-PL]) framework built on a proprietary framework, using a proprietary language that runs on a proprietary stack.
In my experience, there hasn't been a lot of cross shopping of these two technologies. A developer who gravitates towards RoR is far more likely to look at a Python framework than ASP.NET MVC. Likewise, an ASP.NET developer is more likely to cross shop something like Java; pick a framework, any framework.
In my opinion, an ASP.NET developer is more likely to cross shop with whatever next technology is marketed by MS or whatever the company they have been working for decides to switch to (be it Java or whatever).
A Ruby, Python, PHP [Name your OSS language/platform] developer is much more likely to switch to Java (maybe not the language, but the platform) than any .Net developer ever would be.
When I started to use RoR around 2006 it was quite difficult to find good documentation. So you had to use Google quite a lot to find something useful. Nowadays RoR is better documented and you can find everything you want to know in a few central places. So people may have to search less to find what they want.
otoh, I would suppose there are a couple of how-to blog posts about both platforms.
http://www.google.com/trends?q=%22asp.net+mvc%22,+%22ruby+on...
Adding python as a keyword probably lowers it a little too much, but at least it starts in 2005 when Django was released and is smaller than rails (I am a python fan, but I doubt django is bigger than rails).
http://www.google.com/trends?q=%22asp.net+mvc%22,+%22ruby+on...
http://www.google.com/trends?q=%22asp.net+mvc%22%2C+%22ruby+...
http://tinyurl.com/258zrcy
You can see that search volume growth for "rails" had been flat for the year before Ruby on Rails came out. Since then, "rails" trended the same as "ruby on rails" at every point in the last six years. Right now, the search volume for "rails" is still trending 10 points higher on the graph than it did before RoR came out; to put that into perspective, searches for the full name "Ruby on Rails" have been less than 10 points since the start of 2008. All this indicates is that people have learned they can get good results by typing "rails" instead of the full name.
I want to add that it's possible that nearly all correlation between "rails" and "ruby on rails" is due to the possibility that google double-counts "ruby on rails" searches as "rails" since that word appears in the full name. However, the 10 point increase in "rails" still trends 5 points higher than the 5 point increase in "ruby on rails" during the same period of first release in 2005 to now in 2010, which is double. But anyway, the point isn't that my stats are any better; the point is to demonstrate that it's hard to make an inference based on two keywords, and even harder to predict what will happen based on this information, even if it was accurate.
No news here except that there are many MVC web frameworks these days.