>> In the process of getting rid of ASP.NET repeaters and instead uses the append string thing or response.write...
Even as a long time .NET developer, I don't believe .NET is optimal for Internet Start-Ups. Most of the pro-web talent are in Ruby/Python/node.js camps where they enjoy first class support of all the popular web DSL's (e.g. less, sass, jade, handlebars, etc). As well as all the bundling, optimization and minification tools which were available for years in other platforms and have only recently been a supported option in .NET with System.Web.Optimization. The pro-web (Single Page App) community is relatively non-existant in .NET. E.g. none of the showcase apps on http://backbonejs.org (the most popular SPA JS fx) are in .NET.
The ASP.NET website packaging model doesn't scale (productivity-wise), since the larger the website becomes the slower build/iteration times get - which is especially important for start-ups. I do believe typed languages are better suited for typed back-end services - I just no longer believe in them for fuzzy development tasks like UI/HTML generation, automated scripts, etc.
That may be so but when selling software to large enterprises then .NET really helps. I think I would be safe in saying that most enterprises will have Windows OS somewhere in the data center. We've just built a product from the ground-up using MVC 4 (yes, beta) and it is just about to ship -- plenty of pre-orders already and the IT Police just let's us "in".
.NET is the only way I would personally want to go when targeting large enterprises with products.
