Re: Is ASP.NET outdated?
- From: "Kevin Spencer" <spam@xxxxxxx>
- Date: Wed, 27 Dec 2006 08:23:10 -0500
To say that ASP.Net is outdated is to say that an entire segment of the .Net
platform, and perhaps of the Internet is outdated. ASP.Net is much more than
a programming technology for creating dynamic web pages. It is a server-side
HTTP technology that supports a whole plethora of sub-technologies,
including Ajax and Web Services. They all have one thing in common: They
handle HTTP requests, and return HTTP responses to a client software.
As for Open Source, no doubt, it has its' place in the world. But it is
nothing new, and it will never replace Microsoft technogies, or any other
major non-Open Source vendor technologies. There is something to be said for
using products and technologies that easily interconnect, and that is what
Microsoft has been about for as long as I've known them.
--
HTH,
Kevin Spencer
Microsoft MVP
Bit Player
http://unclechutney.blogspot.com
A pea rants as candy be sieving.
"darrel" <notreal@xxxxxxxxxxx> wrote in message
news:u4zUdVUKHHA.1280@xxxxxxxxxxxxxxxxxxxxxxx
ASP.NET (and ASP.net 2.0) is based on framework from 2000. It was a great
stride forward at that time, the other popular option at that time was
jsp/ejb. Since that time a major paradigm shift caught on, specifically
ajax and Ruby on rails. The most important I feel is the positive effect
open source now has on a framework.
From a technical standpoint, I'm really not skilled enough to say.
But from a 'vibe' standpoint, yes, It seems that asp.net is outdated. But,
for that matter, I guess it seems that many of the systems are outdated by
that defnition.
If it's not open source, and not PHP or ROR, then it just doesn't have
that web 2.0 'vibe'.
Sure ASP.NET AJAX now allows AJAX. Correct me if I'm wrong here but its
far more expensive than other frameworks.
ATLAS is free. ASP.net is free.
IIS isn't, of course.
It seems like there is a lot of complexity to get ajax to work in the
asp.net framework. This complexity doesn't exist in other frameworks. Not
to mention there seems to be some quirky issues with asp.net ajax (which
might be my fault due to improper use).
I think the big thing (and this is my impression) is that MS's framework
is all about integration.
IIS integrated with MSSQAL integrated with ASP.net integrated with VS.net
integrated with reporting services integrated with Sharepoint, etc.
They've built this great, robust system, and targeted it at enteprise
application developers.
And for that, I have to say, it works great.
But it's not as ideal for the next web2.0-I-hope-we-get-bought-by-google
web site for a number of reasons:
- it's heavy. ATLAS is a beast. Not a big deal on an intranet. Perhaps a
big deal on the web at large
- it's not free. Startups like free (as in open source)
- the community is a bit lopsided (mostly fellow entrprise software
devlopors)
So, yea, I guess I feel the same way. I feel a little bit out of the loop
sticking with ASP.net
-Darrel
.
- Follow-Ups:
- Re: Is ASP.NET outdated?
- From: Joe (MCAD)
- Re: Is ASP.NET outdated?
- From: darrel
- Re: Is ASP.NET outdated?
- References:
- Is ASP.NET outdated?
- From: Joe (MCAD)
- Re: Is ASP.NET outdated?
- From: darrel
- Is ASP.NET outdated?
- Prev by Date: Re: GridView Question
- Next by Date: Re: GridView Question
- Previous by thread: Re: Is ASP.NET outdated?
- Next by thread: Re: Is ASP.NET outdated?
- Index(es):
Relevant Pages
|
