Re:Linux isn't the be all and the end all... (Score 2)

I'd like to make a counter point as to why I think Linux would make a good choice for embedded solutions. Note that I have several years experience as an embedded software engineer so my opinion my be a bit biased :)

Let's start with product development. When it comes to the operating system, whether it be a simple task switching executive or a full fledged operating system like Linux, WinCE, QNX, etc., there are 2 routes to take. One, roll your own or two, get one off the shelf. Rolling your own is extremely expensive to a company. Not only does it cost money to pay for the engineering, but it takes engineers away from working on the actual application of the product. That leaves getting an off the shelf opoerating system. (Admittedly, off the shelf operation systems won't work in all cases, but generally they get job done.)

To continue with product development... The ability to run an embedded product's code on your development workstation and the embedded device is a tremendous advantage. Host side development tools tend to be easier and more reliable. The API on a Linux workstation happens to be identical (with vfew exceptions)to the API on an embedded device running Linux. WinCE has a similar but slightly incompatible API to Win32. Target side development tools are more difficult and less reliable because they tend to rely on precisely setup configurations. Not to mention that there is an added step to trying out new code when you fix a bug. With target side debugging you have download the new code after each build which could take longer than the build depending on method of communication with the target.

Most readers of Slashdot know about the Linux kernel's configurability and modularity, so I wont spend too much time on that. Suffice it to say you only compile in support for stuff you need like SMP (which very few embedded projects need).

Networking. More and more embedded devices need networking support. The Linux kernel with various userland programs provides a rather complete set of networking capabilities. Whether it be serving web pages describing system status, web browsing Slashdot on a train through a web pad, or some mundane SNMP control, Linux will fit the buill.

As to Linux's "bloat", when Linux first appeared on the scene almost 10 years ago, 16Meg of RAM was prohibitively expensive for mony desktops, much less embedded devices. However, 16Meg today is nothing. 16Meg will fit on a single chip instead of several SIMMs. The capacity of hardware has grown much faster than the size of the Linux kernel.