ok, after hearing this $%#@ i thought i would weigh in with a REAL example of how much ASP sucks and how incredibly powerful WO is -- you need skill and talent to be a WO developer, as someone else said, anyone can be an ASP developer. when Dell first developed their on-line store they used some technology that is irrelevent for this discussion. their return rate -- i.e. misconfigured products -- was about 10 percent. things like ordering a SCSI HD with no SCSI controller were a common example of misconfiguration. but hey, what does the average home user know about building a computer? so they said, we need something better. so they turned to WebObjects -- which was then owed by NeXT. it took a handful of NeXT engineers about 3 months to put together the Dell store. once the Dell store was on-line with WO the return rate went from 10 percent to 3. not 3 percent, but 3 actual returns due to misconfigured products. now, fast forward to 1997, Apple buys NeXT and this looks bad: Apple technology is running the Dell store. so what happens next? Microsoft to the resque. it took a TEAM of MS engineers over 9 months to reengineer the site in ASP. on top of that the site did not have anywhere near the same functionality as it did when it was run by WO. and, and this is a HUGE and, the site went from being served on 4 large Sun server to being served from over 75 machines running Windows NT. a pretty compelling argument that says ASP is not industrial class stuff. it is great for a small site or a site run by people who suck bill gates' you know what, but it is not a serious development tool. and to correct someone else, WO can be developed on Mac OS X Server -- and soon OS X -- and NT and can be deployed on OS X Server, NT and solaris for sparc. it can also connect to oracle, sybase, informix, etc., throught adaptors not ODBC as someone else said. you can do increadible data modeling with WO which you CAN NOT do with ASP. and with WO, as the name implies, you deal with data as objects that can be munipulated just like any other application object. try to do that with ASP.
Slashdot Mirror
i don't know where you've been living, but you can deploy oracle enterprise server (8i) on linux. you can get 8i for around $3000.
ok, after hearing this $%#@ i thought i would weigh in with a REAL example of how much ASP sucks and how incredibly powerful WO is -- you need skill and talent to be a WO developer, as someone else said, anyone can be an ASP developer. when Dell first developed their on-line store they used some technology that is irrelevent for this discussion. their return rate -- i.e. misconfigured products -- was about 10 percent. things like ordering a SCSI HD with no SCSI controller were a common example of misconfiguration. but hey, what does the average home user know about building a computer? so they said, we need something better. so they turned to WebObjects -- which was then owed by NeXT. it took a handful of NeXT engineers about 3 months to put together the Dell store. once the Dell store was on-line with WO the return rate went from 10 percent to 3. not 3 percent, but 3 actual returns due to misconfigured products. now, fast forward to 1997, Apple buys NeXT and this looks bad: Apple technology is running the Dell store. so what happens next? Microsoft to the resque. it took a TEAM of MS engineers over 9 months to reengineer the site in ASP. on top of that the site did not have anywhere near the same functionality as it did when it was run by WO. and, and this is a HUGE and, the site went from being served on 4 large Sun server to being served from over 75 machines running Windows NT. a pretty compelling argument that says ASP is not industrial class stuff. it is great for a small site or a site run by people who suck bill gates' you know what, but it is not a serious development tool. and to correct someone else, WO can be developed on Mac OS X Server -- and soon OS X -- and NT and can be deployed on OS X Server, NT and solaris for sparc. it can also connect to oracle, sybase, informix, etc., throught adaptors not ODBC as someone else said. you can do increadible data modeling with WO which you CAN NOT do with ASP. and with WO, as the name implies, you deal with data as objects that can be munipulated just like any other application object. try to do that with ASP.