W3bbo wrote:

odujosh wrote:
Productivity is more important than technical purity.


But I feel ASP.NET's Server-Side Events for controls are a hinderance to productivity since they clash with my developed understanding of HTTP and the stateless web.

It also makes it harder to develop truely portable and compatible webapps.


I will agree that if you goal is to run on whatever flavor web server this could be an issue. Every project I have worked on they are more than happy to lock in on a Server platform. Even for amateurs hosting providers abound that offer both Windows and Linux Servers. (the prices are very similair and range with what support and features you want)

If you talking about browser compat. Your server platform choice does not absolve you of handling differences in browsers rendering, so this has nothing to do with choice of server side platform. All server side technologies I know of (PHP, ASP.NET, ASP, CGI) are pretty client angnostic unless it some technology dependency (javascript is a great example). Client agnostic is half the point I think. I have done a CMS (Content Management System) that a team that all used MACs used to post articles to a site using ASP.NET. So as a client you could care less if it is PHP or ASP its all abstracted away by the time it reachs you.

ASP.NET is a tool not a requirement.

Maintability may be another issue you want to look into with you line of thinking. Although you may understand what your doing it your code. Will the next guy have to base his disertation around it to understand the subtlties. I think of this as code weight. Is what I wrote documented and clear. Or do I need to take a perl class to begin to understand what @#$@$# means Smiley