Aristotle denounced written language saying it'll have a bad effect on human
memory.
Anyway, in a *real* enterprise app, you'll still be writing a whole lot of
code. The MS built in stuff that ships with ASP.NET 2.0 isn't suitable for a
multi portal architecture. Much of it is real cool but also will not work
downward compatible on Netscape 4.x.
You might ask why bother with that? Every government site has to be Section
508 compliant and the cool breadcrumb/treeview etc. are not. Not to mention
web parts/treeview are very very microsoftish - when it comes to designing
websites that are intended for huge audiences, your designers will more
often than not choose a non microsoftish look.
Consider that you are developing amazon.com, and consider what all ASP.NET
2.0 built in stuff will you be able to use? Your site must support every
browser out there, it has to be just as presentable to a non-logged in user
as it is to a logged in user. Can it be developed in ASP.NET 2.0? YES SURE
!! Is it a 2 day job? HELL NO !!
Look at any other big commercial website. You will find the same situation.
None of those are out of the box implementations with even ASP.NET 2.0. Or
atleast as much as they'd like you to believe, they are not.
Secondly, in ASP.NET in general, microsoft has been very very very very very
very security heady. (Read this
http://dotnetjunkies.com/WebLog/sahilmalik/archive/2004/10/28/30241.aspx ).
While I cannot argue that security isn't important, I feel in this entire
rhetoric of creating unbreakable security and creating more and more cool
stuff around creating things more and more secure, a few other important
facets are getting missed out. These could be skinning/layout/content
management/browser compatibility/failover schemes/memory
management/alerts/redundancy etc. etc. etc. Think about it - SQL Server and
IIS are both "Servers". They both have equally important roles. But SQL
Server is so much more mature, and IIS is so ultra lame in comparison. Yes
they serve different purposes, but that doesn't mean IIS (or web servers in
general) doesn't have room for improvement. The initial web servers were
written to deliver content, and we are beating the same dead horse today to
run SAP applications. C'mon !! Can we not come up with something better?
If I had to name two products that have stopped in the passage of time, it'd
be IE 6, and IIS 6. These two have failed to evolve when we moved from VB6
to .NET, from SQL Server 7 to Sql Server 2005.
Not to mention I've met very very few developers who really understood .NET
security, which means they implement their own much more home grown
vulnerable concoction. Yes what they do is incorrect, but it does happen.
Anyway, bottom line - ASP.NET 2.0 is an improvement, and if it were so cool
that it could put you out of a job, they'd probably had written a cool
utility called MakeMySite.Exe .. but there is no such utility so yes you
will still have a job. As a matter of fact, the improvmenets in ASP.NET 2.0
will force the few idiots who are still stuck on JSP to finally convert
over, and the job pool will actually increase.
.............. However (man I just keep going) ....... I feel that with the
introduction of ClickOnce, and eventually with Longhorn, when web based
XAML/Avalon applications show up. And the firefox XUL attempt are harbinger
to deathblows to HTML based web apps. And rightfully deserved so, HTML
sucks, it limits you so much, and the way it came into
development/evolvement was netscape and ie fighting over each other, it is
in essence the grandaddy of VB 6, i.e. it decides to ignore your mistakes to
be ultra compatible. What that gives you is a completely non-standard
uncontrollable look and feel and a very very tied hands developer that
cannot take advantage by far of the rich underlying protocols that could
seriously make the internet SO SO SO much more worthwhile than Internet
Explorer and HTML let you.
I feel in ClickOnce we see the beginning of the end of HTML based web
platforms, this change might take 5-10 years even, but it will happen IMHO.
The best part about ASP.NET 2.0 is that you don't have to use it
- Sahil Malik
http://dotnetjunkies.com/weblog/sahilmalik