Microsoft Throws Down Embedded XP Gauntlet
An Anonymous Coward writes: "Microsoft has published an online document entitled 'Why Microsoft Windows XP Embedded and Not Embedded Linux?', in which embedded XP is compared to Embedded Linux in eight ways. Given that fact that 'Embedded Linux' is not the product of a single dominant vendor, but rather is the result of the collaborative (and competitive) efforts of
an entire market consisting of dozens of large and small companies plus thousands of individual developers, LinuxDevices.com is inviting the Embedded Linux Community to respond to 'Why Microsoft Windows XP Embedded and Not Embedded Linux?' through guest editorials and talkbacks."
http://www.microsoft.com/Windows/embedded/xp/evalu ation/compare/notlinux.asp.
rOD.
Rod Begbie done this, and he's not
Calm down - that is standard boilerplate. Pointing it out is akin to yelling about "forward-looking statement" disclaimers in press releases of public corporations.
Don't worry. Microsoft have enough law-suits on their hands already, so their Embedded XP license explicitely forbids such use. Good for them - and good for us emebdded developers because for most of the interesting uses (medical, automotive), we are simply not allowed to use Embedded XP. Minimum footprint at 4.8 MB? Yikes!
My opinion? See above.
And one of my favorite quotes:
Now, if you were, say, flying an aircraft, knowing Microsoft's track record, would you trust Windows XP Embedded to keep you in the air?
And frankly, they're trying to compare Windows XP to Linux. Window managers? Who the hell uses Window managers in *most* embedded devices? I'm not talking Palm pilots here - I'm talking refrigerators, toasters, watches, automobiles, TVs, stereos, etc. And no drivers for embedded architectures besides x86? How about StrongARM, PPC, and every other supported CPU?
Really, this is just sad. And the worst part is that many of the people who make decisions will believe this because they don't know any better. Anyone care to write up and post a VALID comparison? Lineo? Perhaps another embedded linux vendor? Embedded Linux Journal?
Embedded linux is so great because it comes entirely in source. The embedded market is the embedded market so you could do things to the drivers to adjust the operating system to your needs.
Let's say you want to build a hard-real-time audio processor, with windows such a thing is simply impossible, because adjusting the scheduler is not something you will be able to do. Furthermore the driver for the audio card IN SOURCE is required to test for problems there.
In my experience you can get an embedded linux kernel running on 3 megs of flash and 16 megs of ram (they didn't have anything smaller, so excuse me).
There are a lot of useful projects working with embedded linux (see opensource.lineo.com. let's see them duplicate those first. Also software that works on linux can simply work, without modifications (although people tend to make it somewhat smaller) on embedded linux.
As someone who works in the embedded networking area, we laugh at Microsoft. One reason embedded Linux is making inroads is that it supports a wide variety of processors and architectures. Windows XP will not run on Power PC, Mips, or a variety of other platforms. Also, it is much easier to write embedded code for Linux just because it is open source.
VxWorks is also popular (but it's very $$$ with full source) because it can run from a very small footprint. The last project I worked on had a flash footprint of around 1.6MB and ran quite well with 8MB of RAM (this was a L3 switch with a lot of additional proprietary software).
Many embedded areas don't care about wiz-bang user interfaces or multimedia. Also, with embedded Linux there are some nice alternatives. There is an embedded version of QT and KDE that do not require X Windows that includes a full-featured web browser that better follows the standards than IE.
Also, getting close to the hardware is much easier in Linux than Windows. Writing kernel loadable modules is a trivial task for Linux, and setting up communications between user and kernel drivers is also trivial (through ioctls or even the proc filesystem).
Linux also comes with a wealth of sample code from which to base a driver or application. With Windows you get whatever comes with the DDK, whereas with Linux you get the source to every non-proprietary driver available.
Embedded developers also like to have the full source code to everything. When something goes wrong, we don't have time to wait for a 3rd party to fix a bug. Can you imagine waiting for Microsoft to fix a bug that only affects a few people?
-Aaron
This post is encrypted twice with ROT-13. Documenting or attempting to crack this encryption is illegal.