> Can you wonder why a large corporation would rather go with ASP for most
> web apps as long as it gets the job done and it's pain threshhold is not
> too high. Same with reasons for going with NT as a File Server or WEb
> Server. Sure it sucks for sophisicated stuff ,but 90% of places don't
> really need sophisticated stuff.
>
> They need cheap and easy to find programming help to whip custom shit
> out. With some emphasis on cheap.
That's an excellent point: If you need cheap shit, ASP is the tool for
you!
[Sorry... I couldn't resist... ;-) ]
But honestly, sure, there's a place for ASP (and NT as a web/file/print/
etc. server), and it's exactly where you describe. Most places just
need something to kind of work, most of the time, in a fashion that's
easy enough to let your summer intern take care of. (Or your MSCE --
same diff. ;-) Sorry... I couldn't resist again.)
But there is also a place for technologies that actually do the
_right_ job _exactly_.
The problems come up in two places:
* when you think you only need 80% of the job done and you go
with NT, and then you find out that your ass is in a sling if
you can't get the other 19% figured out, and soon!
* when you try to go with the 99% solution, but find you're
not up to the task, not up to hiring the people who are, don't
provide the time to train and learn in order to treat the
technology appropriately, etc.
Everyone's walking a fine line in so many regards... we all just
try to do our best.
Cheers,
Richard
-------------------------------------------------------------------------
Richard Dice * Personal 514 816 9568 * Fax 514 816 9569
Open Source Evangelist, HBE Software * http://www.hbesoftware.com
ShadNet Creator * http://shadnet.shad.ca/ * [EMAIL PROTECTED]
Occasional Writer, HotWired * http://www.hotwired.com/webmonkey/
"squeeze the world 'til it's small enough to join us heel to toe"
- jesus jones
