Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Interesting Article


  • Please log in to reply
2 replies to this topic

#1 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,090 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:01:45 AM

Posted 01 October 2006 - 08:55 AM

I just read this interesting article. It appears to explain why Windows is such a mess - and how it happens.
http://www.microsoft.com/technet/technetma...al/default.aspx

Synopsis: There's one approved way to call a function in Windows. But software programmers often use other methods - and this is what makes it so hard to keep Windows compatible with applications.

In this example they used Mapped Network Drives. There's a function that will call the Map Network Drives that can be used to do this directly.

But, the programmer decided to call the right click menu of Explorer to get it. And, instead of picking the name from the menu, they just picked the 3rd entry from the top. Then, they realized that it was different between WinXP and Win2K - so they added a version check to it. Then the user enables AutoPlay - and it bumps the item down - so they went back and defined it as the 5th item up from the bottom (rather than the 3rd item down from the top). Etc, etc, etc.

Now, there's no way that Microsoft can know exactly what each programmer in the entire world has done (but they're trying with the different hardware and software certification programs that they use).

Then along comes Vista with even more changes to the context menu. How can Microsoft be sure that this program will work with Vista?

You may say that it's the programmer's problem - but it's not, it's the user of the program's problem. They're the one that will have to wait for a patch to fix this - and they may lose a contract or some business because of it.
My browser caused a flood of traffic, sio my IP address was banned. Hope to fix it soon. Will get back to posting as soon as Im able.

- John  (my website: http://www.carrona.org/ )**If you need a more detailed explanation, please ask for it. I have the Knack. **  If I haven't replied in 48 hours, please send me a message. My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)FYI - I am completely blind in the right eye and ~30% blind in the left eye.<p>If the eye problems get worse suddenly, I may not be able to respond.If that's the case and help is needed, please PM a staff member for assistance.

BC AdBot (Login to Remove)

 


#2 jgweed

jgweed

  • Staff Emeritus
  • 28,473 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Chicago, Il.
  • Local time:12:45 AM

Posted 01 October 2006 - 09:11 AM

Trying to maintain backward compatibility, as well as interface new modules into an older framework of code, has been a major problem with MS. To be fair, it is a monumental task given the economic necessity of producing a new version every other year or so, and to meet deadlines, they have not done it with much elegance.
Cheers,
John
Whereof one cannot speak, thereof one should be silent.

#3 Enthusiast

Enthusiast

  • Members
  • 5,898 posts
  • OFFLINE
  •  
  • Location:Florida, USA
  • Local time:12:45 AM

Posted 02 October 2006 - 03:41 AM

Poorly written or non-compliant code is also one of the major reasons for the existence of the seemingly never ending discovery of exploits, most of which are unfairly blamed on Microsoft.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users