|
I did fail to mention that the developer blamed much of the difficulties on the underlying O/S. Such phrases as 'Windows isn't consistent in it's response to this or that call so we crash will communicating with the hardware' were bought up often. So far this year we have only had the software cause one BSOD but that's still one more of those than I need to deal with while 80 or more high school girls in swim suits stand there staring at me. OK well maybe the scenery is OK but their parents are ALSO staring at me so that IS bad. :-(
- Larry Walden H. Leverich wrote:
Larry, The crappy code written by the developer has _nothing_ to do with Microsoft -- sorry. I can write just as crappy code on the iSeries. I can make RPGxxxx errors appear all over the place, not to mentionCPFxxxx and the occasional MCHxxxx.Granted, the barrier to entry in the PC market is so low that any schmoe can write and release code, but you can't blame a programmer's stupidity on MS. -Walden
As an Amazon Associate we earn from qualifying purchases.
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.
midrange.com
