R
Rob R. Ainscough
I realize I'm learning web development and there is a STEEP learning curve,
but so far I've had to learn:
HTML
XML
JavaScript
ASP.NET using VB.NET
..NET Framework
ADO.NET
SSL
FormAuthentication
(and probably a few more things)
Now call me crazy, but this hog pog of languages & technologies is
ridiculous!! The simplest of tasks become major R&D efforts (setting the
enable state of a control on another ASPX page in a frame for example). And
XML, OMG that has got to be the most ineffecient way to write out data I've
ever seen -- the overhead is staggering!! So far the research I've seen are
"frames are evil" -- great so freakin' helpful. This is just crazy, if the
development community has to continue on in this bizarre environment of
languages and technology, then web application development is never going to
mature and become cost effective for companies to exploit.
This is NOT an efficient way to get work done -- just the cost to get
developers up to speed on all the technology can doom a project from the
start. The pipe dream of using ASP.NET with VB.NET and .NET framework ONLY
for web development is just that -- a pipe dream, for only the simplest of
applications could anyone get away with just those three technology/tools.
I just don't understand -- terms such as portability get tossed around, but
the bottom line is, if you elect to use .NET Framework and ASP.NET your
bound to MS server OS. And, if this is all done in the name of
"portability" (at the cost of performance) how often are you folks moving
servers around and changing platforms?? If platforms are changing that
frequently, that begs the question why?! It's like building something for
5% that may need it while the majority don't -- so the majority have to take
the penalty. There has got to be a better way?
Rob.
but so far I've had to learn:
HTML
XML
JavaScript
ASP.NET using VB.NET
..NET Framework
ADO.NET
SSL
FormAuthentication
(and probably a few more things)
Now call me crazy, but this hog pog of languages & technologies is
ridiculous!! The simplest of tasks become major R&D efforts (setting the
enable state of a control on another ASPX page in a frame for example). And
XML, OMG that has got to be the most ineffecient way to write out data I've
ever seen -- the overhead is staggering!! So far the research I've seen are
"frames are evil" -- great so freakin' helpful. This is just crazy, if the
development community has to continue on in this bizarre environment of
languages and technology, then web application development is never going to
mature and become cost effective for companies to exploit.
This is NOT an efficient way to get work done -- just the cost to get
developers up to speed on all the technology can doom a project from the
start. The pipe dream of using ASP.NET with VB.NET and .NET framework ONLY
for web development is just that -- a pipe dream, for only the simplest of
applications could anyone get away with just those three technology/tools.
I just don't understand -- terms such as portability get tossed around, but
the bottom line is, if you elect to use .NET Framework and ASP.NET your
bound to MS server OS. And, if this is all done in the name of
"portability" (at the cost of performance) how often are you folks moving
servers around and changing platforms?? If platforms are changing that
frequently, that begs the question why?! It's like building something for
5% that may need it while the majority don't -- so the majority have to take
the penalty. There has got to be a better way?
Rob.