Live data from Hacker News

How We Moved From Microsoft ASP.NET to Rails and NoSQL

infoq.com

61–70 of 101 posts

Re: How We Moved From Microsoft ASP.NET to Rails and NoSQL

#61
post #3

As an MS developer this really is devastating. Rob Conery is one of the names that any fan of ASP.NET MVC knew. He was involved in the project when he worked there (I'd call him the most high profile MS employee aside from Scott Guthrie). To have him come out and say he couldn't make a startup work with Microsoft technology really tells you all you need to know about that. I still need to use .Net at work but I think…

In the exact same position. .net by day, anything else by night.

Re: How We Moved From Microsoft ASP.NET to Rails and NoSQL

#62
I've got a small webapp targeting ASP.NET MVC 2.0 (built with Visual Studio 2010) running on Linux with Mono 2.6 and served with nginx (using the fastcgi interface to mono) so if you put the time in, it's possible to deploy on an open source stack.

I saw a commenter talk about Linq-to-SQL and yes this is possible too. I use a PostgreSQL server and use Linq-to-SQL with it. It works but as expected, the documentation is poor.

This is free to use, but from my experience some of the costs can be very frustrating time spent trying to figure out why things are not working as they should, or barrier to entry with poor documentation.

As one commenter pointed out, mono behaves strangely when changing part of your codebase while it's running. Modifying a file can cause 500s or timeouts to be thrown. Killing and restarting the fastcgi process is needed.

A major positive is the developers who work on these parts of mono are very responsive to issues and code is improving all the time.

Re: How We Moved From Microsoft ASP.NET to Rails and NoSQL

#63
post #59

Earlier quoted context omitted.

Because it's a robust and feature rich database/tool-set thats great to develop on and gives me peace of mind. It's been a while since I used MySQL but the database and it's tools left me underwhelmed. I found that I could be more productive with SQL server. I haven't tried Postgres. I guess I like to think if my databases grow too large for the free version that's a good problem to have. It's not that bad a "time-bo…

You can't even do automated backups with SQL Server Express (without some hacks or other tools). MySQL is a pleasure to work with and so it MongoDB, more so than SQL Server. If you prefer SQL Server than more power to you.

http://stackoverflow.com/questions/122690/what-is-a-simple-c...

Re: How We Moved From Microsoft ASP.NET to Rails and NoSQL

#64
post #59

Earlier quoted context omitted.

Because it's a robust and feature rich database/tool-set thats great to develop on and gives me peace of mind. It's been a while since I used MySQL but the database and it's tools left me underwhelmed. I found that I could be more productive with SQL server. I haven't tried Postgres. I guess I like to think if my databases grow too large for the free version that's a good problem to have. It's not that bad a "time-bo…

You can't even do automated backups with SQL Server Express (without some hacks or other tools). MySQL is a pleasure to work with and so it MongoDB, more so than SQL Server. If you prefer SQL Server than more power to you.

I do backups using a windows scheduled batch file that runs sqlcmd.exe (part of sql express). Slightly hackish but it gets the job done.

Anyway, I hope that articles and interviews like yours do make MS lower the price of SQL standard, but people shouldn't dismiss the MS platform based on cost when in many cases it could be almost free.

Re: How We Moved From Microsoft ASP.NET to Rails and NoSQL

#65
post #56

Earlier quoted context omitted.

Your assumption here is that the blame game somehow is the path to productivity and "the answer". This, to me, means you have a lot of other problems where you work - your platform doesn't matter at all. You're very right, however in that no one gets fired for using Microsoft - but that's changing. Don't take my word for it - ask the guys in Building 42 - they know it too. You touch on a very particular, hot topic in…

I don't agree with your points on human nature. On blame, every executive staff of a large company that I've ever seen casts blame. Yes there are startups with a small number of people that are all pretty even keel but as soon as you get to a certain size you'll get opposing interests and that's where blame comes from. The blame game is a political game played by people trying to get leverage over other people in ord…

I'm just glad you haven't gotten any downvotes yet ;)

Re: How We Moved From Microsoft ASP.NET to Rails and NoSQL

#66
post #43

I have learned Ruby on Rails and I am amazed that after three weeks with RoR I am more productive than after 10 years with .net I reported my own experience moving from Asp.net to Ruby on Rails in my blog a few days ago: "How an experienced developer multiplied his productivity tenfold" http://aymeric.gaurat.net/index.php/2010/how-an-experienced-...

Did you happen to try out other frameworks before deciding on RoR? I'm thinking about testing the waters outside of MS land and I'd like to know why you chose RoR versus, say, Django or even Struts.

I find it hard to imagine that there is any web framework still around that could be more screwed up than Struts. After having had some major exposure to the various members of the Struts family and Rails, I would say that the experience of using Struts 2 is slightly worse than using Rails while being flogged by an expert torturer. :-)

If you want to test the world beyond MS I would recommend (apart from Rails or Django) looking into the Scala/Lift (my preferred toolset), Clojure/Compojure or JavaScript/Node.js combos (depending upon you language preferences).

I would be careful with Rails, when you plan to do some heavy data processing and/or if you need your application processes to run for a long time without being restarted.

For small, straightforward applications or prototyping the Ruby/Sinatra/MongoDB combo is also really really nice.

Re: How We Moved From Microsoft ASP.NET to Rails and NoSQL

#67
post #35

Earlier quoted context omitted.

We didn't seriously look at Azure for a couple reasons: 1) It's expensive compared to other hosting platforms. 2) I hate lock-in to a particular platform. If we coded against Azure tables we would be locked in to Azure. If we used their SQL platform we would be space constrained. 3) I have used Azure and deployment, updates, and troubleshooting are all slow and cumbersome. It is still a very immature platform.

We're looking at making the move from Rails to ASP.NET MVC. So pretty much the opposite of what you've done, and we're planning on hosting on Azure. So I read this thread with great interest. We've found that like for like the Azure platform is very well priced and is actually less expensive than our current Ubuntu setup, as well as being cheaper than comparable high level Microsoft hosting providers. We don't much l…

Surprising to hear that Azure is cheaper for you, I would be interested in hearing if that holds true once you actually get up and running on it.

I actually used a powershell script to automate deployments on Azure, it was the delay from when you do that which is so frustrating. Waiting 5-10 minutes was fairly normal.

Re: How We Moved From Microsoft ASP.NET to Rails and NoSQL

#68
If you're an ASP.NET MVC programmer looking to learn Ruby on Rails, check out my book Ruby on Rails Tutorial at

http://www.railstutorial.org/

I don't know ASP.NET MVC at all, so I haven't tailored the presentation to Microsoft developers, and I'd be curious to hear if you find my approach accessible. You can leave me feedback at http://www.railstutorial.org/feedback.

N.B. Although NoSQL is outside the scope of an introductory tutorial, I'm hoping to do some follow-on articles on such specialized topics once the core tutorial is finished. (I'm currently writing the final chapter.)

Re: How We Moved From Microsoft ASP.NET to Rails and NoSQL

#69
post #19

Earlier quoted context omitted.

I would've loved to see a rough breakdown of how they got the the "5 figures" cost...

SQL Server license: $7171 per processor - we have a single quad machine... which we'll likely need to split into two machines, incurring extra licensing fees. Our servers were hosted at MaximumASP and they gave us a bandwidth quote with additional servers that was 4 figures (remember, this is 3 years out). Visual Studio is $1200 a pop - this is for two people. I'm already at 5 figures and I didn't include Expression/…

You really don't HAVE to use SQL Server just because you're using .net you know...

Re: How We Moved From Microsoft ASP.NET to Rails and NoSQL

#70
post #57

Earlier quoted context omitted.

Tell that to MySQL which runs like an ape through a mud bog on Windows.

Then put MySQL on a Linux box, no need to have it on Windows...

And then you have the added complexity of two OS platforms to support.....

I think they made the point in the article that they could have overcome the obstacles of the ASP MVC platform, but why? They said they're more productive on Rails, they like working on it better, and it's cheaper.

What positive would there be (for them) of staying on the MS platform?

Post reply on HN