Slashdot Mirror
First, WinModems. Now, WinWiFi.
zulux writes "Microsoft is actively encouraging WiFi (802.11b) hardware manufacturers to strip their devices of costly electronics, and use Microsoft software/drivers to make up the slack. And you thought WinModems were bad!"
First, WiFi devices have been out for a few years now. Yeah, hardware modems had been too, but the markets are moving faster now than they had been 10/15 years ago. Furthermore, there's already a new big player in the WiFi market that won't stand and let Microsoft have exclusivity on WiFi drivers...Apple.
"Mod, mod, mod...and another troll bites the dust."
One way to reduce hardware cost is to put hardware functions in software.
You don't see anyone calling "monopoly" about software RAID cards, and those that do pay far more (andget only marginally better performance) from hardware RAID.
Winmodems may be a PITA for us, but you can get then for $5, vs. $70ish for a hardware modem (the 3Com Performance Pro comes to mind)
I can see that Microsoft may look at this as another opportunity to extend the duration of their doomed monopoly, but honestly I don't believe that they are morally obligated to keep hardware prices up by NOT integrating their functions into software. They are, after all, a software company.
Does it not make sense to introduce new stolen ideas to make more use of software?
Besides, these are Microsoft drivers. They'll probably be slow enough to help the ailing hardware industry sell a few more chips. That's aid that they could use now.
Yes, I know it isn't kisher to say that not *everything* Microsoft does is evil. Mod me down if you like.
Computer Science is no more about computers than astronomy is about telescopes. --E. W. Dijkstra
It wasn't that many years ago that Microsoft, along with just about everyone else in the PC business with an ounce of common sense, launched a jihad against Intel's NSP (Native Signal Processing) initiative.
NSP was the logical response to Intel's realization that CPU cycles in the Pentium era were becoming less and less valuable to the end user. They considered it a task of strategic importance to soak up extra cycles wherever they could be found... never mind that game developers still needed every cycle they could find at the time. Had NSP succeeded, it would have had a wide array of effects on the PC hardware and software businesses, almost all of them too ugly to contemplate. The nascent market for high-performance 3D and environmental audio hardware would likely have been crushed under the treads of Intel's marketing machine, and WinModems would have taken over the scene years earlier than they did. The development of online gaming technology would have been pushed back indefinitely, pending the ubiquitous adoption of broadband (which, obviously, has yet to happen).
Of course, MS's primary interest in killing NSP was to keep Windows from having to run as just another NSP client. Owning the boot process from BIOS to bluescreen was as important to them in 1994 as it is now. But now, it appears that they've taken leave of their technical senses as well as their ethics. If this is anything like Intel's earlier push to run modem data pumps on the CPU -- and to be fair to MS, the article is by no means clear on this point -- then 802.11 fans, and consumers in general, should fight it where they find it.
Dahlmann tightly grips the knife, which he may have no idea how to use, and steps out into the plain.
I think it's a terrible idea!
Despite the speed of today's CPU's, having to use CPU cycles to do WiFi networking is not a great idea, especially when you also have to take into account for CPU cycles being used for everything else in the system.
I mean, consider the situation of playing DVD discs on a computer. Sure, you can do it completely in software if the CPU is fast enough, but the CPU cycles it requires to do this even on a very fast CPU can drag a system down pretty quickly. Now you know why ATI has Hardware Motion Compensation (HWMC) and Inverse Discrete Cosine Transform (IDCT) decoding assistance on their graphics chipsets starting with the Rage 128 series, and nVidia has pretty much done the same with the current GeForce4 MX/Ti chipset series.