Contact

admin

About Me · Send mail to the author(s) E-mail · Twitter

At GROSSWEBER we practice what we preach. We offer trainings for modern software technologies like Behavior Driven Development, Clean Code and Git. Our staff is fluent in a variety of languages, including English.

Feed Icon

Tags

Open Source Projects

Archives

Blogs of friends

Now playing [?]

Error retrieving information from external service.
Audioscrobbler/Last.fm

ClustrMap

Software Usability

Posted in Geek Mode at Wednesday, October 26, 2005 6:29 PM W. Europe Daylight Time

Yesterday I had an interesting discussion on software usability with Robert. We focussed on operation systems, especially Mac OS X vs. Windows. Neither of us has deep knowledge of Linux, so we just didn't talk about it.

Robert stated that when you've got a Mac you just plug in some kind of hardware and it just works. Unlike as in Windows, no driver needs to be installed and as the OS recognized the new piece of hardware it will happily get along with it. On Windows you have to install drivers and pray that the systems doesn't stop working when the new hardware is initialized.

To my understanding the principles of Plug-n-Play are the same on all operating systems. The implementation might differ, but the interface a PnP device sees and leverages is the same. Installing drivers on a OS is a crucial necessity as no OS vendor will be able to include drivers for all devices that are available. So I won't agree to the statement that Macs don't need drivers.

The Mac hardware platform has been pretty closed during the last years. Apple had almost full control over their hardware and software, so they were able to create a performant OS that comes with a bunch of good-looking eye candy. Windows, on the other hand, tries to reach a far broader hardware market. One may assemble a custom PC and install Windows on it; it's supposed to run. Microsoft had to make sure that the core OS is compatible with a wide set of PC hardware. That definitely is a task hard to achieve when you keep in mind the many possible hardware combinations. It's all about a well defined driver architecture and isolating OS code from device drivers (this is not always possible and/or performant).

Microsoft does not write all drivers for their OS. To protect against possibly bogus hardware drivers they set up the WHQL certification program. A WHQL certified driver was tested by Microsoft and is supposed to be running stable. MS even adds a digital certificate to these drivers as this will prevent displaying the warning message when an uncertified driver is installed. However, the user usually wants to get the hardware to work, so who has ever clicked "Stop installation" when such a message box appeared? Microsoft cannot prevent you from installing those drivers, but you have to keep in mind that this might introduce BSODs by doing so.

Also, every software written by human beings will be prone to bugs. There are secuity holes in Mac OS X as well they are in Linux or Windows or (place your favorite OS here).

Thursday, October 27, 2005 8:51:13 AM (W. Europe Daylight Time, UTC+02:00)
Morgen Axl,


wie ernst nimmst du eigentlich Regel #9 der "Top 10 Blog Design Mistakes" ;) ? Spass beiseite, ULRICH SCHNAUSS rockt vehement! Ich bin von den Socken. Hau rein Kollege,

Christian.
All comments require the approval of the site owner before being displayed.
(will show your gravatar icon)
 
[Captcha]Enter the code shown (prevents robots):

Live Comment Preview