Desktop platforms Toolkit

Story: Microsoft software implicated in air traffic shutdown

Posted by: Anonymous (Wednesday 22 September 2004, 9:33 PM)

This is just another example of how the idiocy and extreme incompetence fostered and legitimized by the MS culture had permeated business and critical computing environments, causing nothing more than disaster after dissaster.

Since many just familiar with a Mickey mouse MS PC or just after swift training to get a MCSE can boast and claim to be a knowleable and expert in computer matters, the MS culture legitimize them, enabling them to get involved in projects and decisions were REAL qualified personel is nothing but mandatory.

No other discipline has suffered so much lost of professional credibility, respectability and polution than the computer sciences field. In the medical field for example, Managed Medicine has managed to poop on the Medical profession, but the limits of the capabilities and competence of the people that work on that field are very well defined, and you don't see a nurse or pharmacy clerk jumping into the operating room to give opinion and get involved in a open heart surgery or other critical medical procedure and be taken seriously. In architecture or Law or virtualy other professions the polution of unquailified people willing to perform jobs for which they simple are NOT qualified is kept under control.

Otherwise we would see the number of deaths in hospitals, or buldings sudenly crashing to the ground increasing in stagering numbers; something that would be anything but acceptable.

On one side it is good that a lot of people have access to computers, but on the other they should know that there is A LOT more that just MS PC's, which is the lowest denominator in computers. But here the rottten part is the MS Software. Being familiar MS PC's or even having an MSCE or any other phony cerification does NOT make anybody qualified in the computer field.

Certainly many people get into the computer field through a MS PC, but if they were to go to College to get a degree or if they were smart enough not to need College education they would discover that there is A LOT more than MS, and that MS related knowledge is limited to the very small, not critical systems. Most of MS experts are neither one. They are MS trained but Computer Sciences ignorant.

There we have in this talk back some of those "experts" whose opinion reveals nothing more than lack of even basic computer field knowledge and incompetence :

" But it sounds like a bug in the application running on the system, which could happen on any system. A unix program with a memory leak would probably eventually crash, too. I know of people who keep Windows itself running much longer than 30 days at a time."

Here is the other :

"What does the OS have to do with anything when you're running a PROPRIETARY SOFTWARE SYSTEM? "

How people like this can call themselves "experts" with a strait face ?. (sofware developer, IT /Network)

In both cases it is obvious that these guys don't even understand that memory managenet policy is a function of any decent OS, which until know NONE of the Windows OS fully have.

If a program has a memory leak, any decent OS, and specially one in a CRITICAL environment should stop that program, while others continue running, and the whole system won't crash.

Any application software PROPRIETARY or not runs on TOP of the OS, it is JUST application software it runs in its OWN USER SPACE, of which the OS has complete control per application, per user, and this is even more important in a CRITICAL environment. Any Unix (AIX, HPUX, TRUE, Solaris, BSD, Linux) does this.

It is obvious that the garbage OS on which the application was running it to blame for such failure.

But the failure began the day incompetent, unqualified, ignorant people were allowed to take part in the evaluation and replacement of the aging system. These people are as much to blame.