Walden H. Leverich wrote:
How come, when MS changes something that makes old code break everyone
yells at MS and points out how we never have this problem on System i,
but when IBM changes stuff that makes old code break it's the vendor's
fault? Hmmmm????

Other people will probably chime in, Walden, but I think it's because IBM gives everybody a long lead time, plenty of notice, and a specific way to address the problem, and it's usually pretty simple. In this case, it's as easy as recompiling your programs. There have been numerous occasions when Microsoft has completely broken backwards compatibility at both the source and object level (VB.NET being one of the classic examples).

But that's just my personal opinion. YMMV :)

Joe

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.