C
Curt Wuollet
Hi Nathan I can answer that last question:
> Why do so many industrial software companies insist on writing their own pieces and plugins for their packages when they do a second rate job compared to existing technologies?>
Because in 5 or 10 years their own database systems will still be supportable rather than obsoleted by MS. And in the meantime, you won't have to change all the interface code that doesn't need changing 3 or 4 times. Often, these decisions are based on past experience and pragmatism. Keeping up with Windows churn is a very expensive part of an ISD's development budget. Also, MS SQL is a resource hog and very much overkill for the job at hand. IT does like to own a new server for each function though. If I were to standardize, it would be on something that fits and can't be obsoleted, perhaps with an API that would work with several other systems. Owning the source would provide even more assurance that you won't be hung out to dry.
Regards
cww
> Why do so many industrial software companies insist on writing their own pieces and plugins for their packages when they do a second rate job compared to existing technologies?>
Because in 5 or 10 years their own database systems will still be supportable rather than obsoleted by MS. And in the meantime, you won't have to change all the interface code that doesn't need changing 3 or 4 times. Often, these decisions are based on past experience and pragmatism. Keeping up with Windows churn is a very expensive part of an ISD's development budget. Also, MS SQL is a resource hog and very much overkill for the job at hand. IT does like to own a new server for each function though. If I were to standardize, it would be on something that fits and can't be obsoleted, perhaps with an API that would work with several other systems. Owning the source would provide even more assurance that you won't be hung out to dry.
Regards
cww