The above commenter clearly misses the main point of the article, which is how to avoid becoming obsolete. This IS a serious issue if you make your living with high-technology, since the way the winds blow does change quickly and often. (For example, six years ago, getting your CNA or CNE was all the rage, and generally brought with it the impression that you're set for life when you've got it. How well are those IPX gurus faring now in today's Internet-obsessive job market?)
...and as far as his opinion of driver support is concerned, I really don't care if the manufacturer of the hardware won't support every single operating system under the sun. I don't think they have to. They can put out drivers for the platforms their software developers are comfortable with to increase the ease of use with that platform, or they can hire people to make drivers for the platforms they want to cozy up to where they don't have the in-house expertise. I am well aware that these costs are a serious issue in the total cost of the final product, but responding to simple inquiries with the information required for a third-party to develop their own drivers costs about the same as any other fifteen to twenty sheets of fax time. Saying "no" to someone who is willing to do the work at no cost or obligation to the company is usually going to be a flawed response. When the cost of releasing the information is so miniscule, compared to the relative gain of having a product functioning under yet another (even moderately popular) platform and increasing the utitilty value of the product, then refusing to release the information to interested developers is a bad buisness move and either reflects a general myopia of corporate management, or bad buisness planning that got them into a situation where they were prevented from releasing the information by an NDA. Either way, it's one rather clear sign that a vendor is not making the right decisions (and increasing the chances that they, too, could become obsolete rather soon).
Why use this one?
This package contains both a client AND a server in case you didn't notice, and the client is the most flexible and configurable implementation around from what I can see. A major benefit is this program has an external shell script that gets called every time the lease is modified somehow, which should be perfect for people trying to maintain updated DNS information (like WINS integration, or roaming DNS services), since you can edit it to your heart's content. It's client also has no "issues" with NT DHCP server implementations, unlike another implementation I could name.