Andrew Stopford's Weblog

poobah

News

Articles

MbUnit Folks

Old Blogs

Is ASP.NET good enough for startup's

James Avery has a link to Jeff Eaton post that asks "Why not ASP.NET [for startup's]?".

Let's consider that if this is a cost thing then it's running Windows (costs) as opposed to Linux (free, unless your paying for support options but its relative). ASP.NET\Visual Studio Express (web edition and c# edition) are free. Jeff's remaining points can be addressed as Webform issues not ASP.NET issues, if your looking for Rails style in ASP.NET then projects like Castle MonoRail shoild be your first port of call. You can find all the power, flexability, community and all that Rails goodness and it's built onto of ASP.NET framework. To be fair to webforms, it's short comings are well know, it's product team is hard working in solving those problems and  as a great community (which extends to the ASP.NET framework as a whole) of users and problem solvers\experts like the MVPs and ASP Insiders.  To address problem 1, if you want to cut costs and run Linux you can still use ASP.NET using Mono. Mono is cross platform (Linux/Mac/Windows) with cross platform tools and is free as in beer (web host availability issues aside). Couple it with MonoRail and you have Rails like development in ASP.NET and costs you nothing.

So why not just use Rails then?

Rails has convention, baked in patterns, baked in testing, powerful language and a powerful framework and yes its all for free. You can hire Rails devs fairly easily and also find Apache/MySql experts easily too. Would you really every need ASP.NET then, you would be able to find webforms coders easily enough but it would trickier to find ASP.NET devs. Finding devs who understand and use things like patterns and testing would narrow your choices down yet more, the problem is that Rails baked this in from the start and the Microsoft way simply does not so in the general case you will struggle. So general availability of devs that grok good software pratice to build your startup app as durable, changeable and scaleable, it's a no brainer.

So what next

As much as I grok Ruby as a language I do love C#, I know each can do things better than the other but technologies like LINQ are exciting. While the spec space in .NET (NSpec for example) is not as complete as Ruby (RSpec) the unit test space is more mature IMHO, RUnit does the work as Rubys xUnit workhorse but MbUnit and NUnit are really pushing at the bounds. The question of patterns and structure will come and over time the style of devs will (hopefully) change too. It is prehaps what I have now and what the potential is for the future, as a startup all of these things need consideration. 

Comments

Brian said:

I think you can also look at this from another angle - who is involved? They generally fall into a few categories:

* Enterprises (not SMEs in general).

* Developers who cater to enterprises.

Enterprises are generally risk averse when it comes to software, unless they exist to build software. Therefore they generally choose safe options (ASP.NET/J2EE), even though the best option might be something else. The 80/20 rule means that make compromises. Startup organisations generally can't make the same types of compromises because they have to gain an audience. To see this in action compare the level of consideration given to UI design and performance for the end user. Enterprises often make many compromises in these areas. Startups who make these compromises are dead in the water.

Startups often have a younger cadre of developers, straight from university. They don't have the baggage a lot of enterprise developers have. Enterprises have a particular culture, benefits etc that attempt to encourage a 9-5 work style, and compromises for political or other reasons. Since startup developers are not exposed to this they look towards the best tools that do the job for them. This means the way they work is alien to enterprise developers. The potential for long work hours etc mean that you have a higher level of automation in some cases, and a duct tape and string approach (until you can afford a better implentation). Tools like Rails are seen as safe to the startup developer because they offer a quality approach that speeds them up, yet has a 'reasonable' foundation.

(All of the above are generalisations and I'm still trying to form my own thoughts in this area. I think it also highlights that a lot of developers would benefit from a little reading on business strategy etc in addition to open source (licencing) etc that many do these days)

# September 5, 2007 11:28 AM

Noticias externas said:

James Avery has a link to Jeff Eaton post that asks "Why not ASP.NET [for startup's]?"

# September 7, 2007 2:44 PM

Emmanouil said:

Cool.

# November 10, 2007 12:14 AM

Paul Shottner said:

Hmm.. I touched on some different issues on my page.

# May 16, 2008 4:34 PM
Leave a Comment

(required) 

(required) 

(optional)

(required)