Re: Is MTS reliable with Oracle?

With the current COM(+) based architecture, you are currently looking at 5 or more updates to an application with a 10 year life span. Shared components are good for code reuse, but even Microsoft violates the core rules that its own architects laid down for backward compatibility and immutable interfaces.

If I were the end customer, I'm not sure that I would be too happy.

But there is a bright side - Microsoft guarantees a rewarding future, as there will be plenty of code to update. ;-)

Mike

Billy Verreynne wrote in message <8alae8$7tj$1_at_ctb-nnrp1.saix.net>... <..snip..>
>
>Maybe it is because I grew up with the old development school. There's is
>still mainframe systems written in COBOL and FORTRAN than we developed back
>in the 80's that are being used today (sure, they needed to be Y2K fixed).
>However, looking at the life cycle of these systems, the cost of
 maintenance
>of the software, it is by far -less- than many client server systems of
>today that has a very short life cycle of 2 or 3 years, attempting to use
>"state of the art" technology and just winding up shooting itself in the
>foot. Repeatedly. With a large calibre hand gun.
>

<..snip..> Received on Wed Mar 15 2000 - 00:00:00 CST