Linux's Future As The Next Embedded OS

CowboyRobot writes "ACM Queue has an interview with Jim Ready about how embedded systems differ from desktops and servers, and how they will help shape the future of Linux. From the article: Your car, for instance, now has telematics -- mapping, navigation, and entertainment systems -- that clearly present a very sophisticated user interface... The neat part for me now is that embedded systems can consist of Linux applications with beautiful graphical interfaces."

Comments

History repeats itself...

[Eneff]

NetBSD runs on everything and is tight, as some of these things are rather resource-strapped.

OpenBSD is secure, doesn't turn on what isn't needed, etc. Thus, it makes a lot of sense for a server.

FreeBSD tries to get a good portion of code running, and is generally the most desktop-friendly, though it is acceptable to servers.
____

Windows CE, Windows XP, Windows 200x Server.
____

G*linux with embedded patches, g*linux with desktop patches, g*linux tweaked for servers...

It's only a matter of time before the code bases start deviating more and more.

New embedded applications will benefit the desktop

[Lurch00]

My sincerest hope is that with all of the embedded applications running on serious hardware now, we'll see an improvement in quality for regular applications. Developing for a sufficiently complex embedded system is indistinguishable for the most part from developing a server application. If you treat your client apps with the same respect you should treat your server apps with, its the same as developing for those too.

I think we're going to see a lot of reuse of existing frameworks and high level abstractions between embedded and traditional applications, and that those frameworks will in turn be hardened to improve their quality. In a lot of situations whole applications will be hardened to run in both variants. This all should in turn benefit the traditional applications. Granted, it still takes a talented developer to produce a quality app no matter how good the underlying framework is. However, I think this type of hardening will help limit the scope of problems to the application code, where the less talented developer is more likely to be able to keep track ot them.

This of course is all dependent on consumers continuing to not tolerate crappy appliances. As long as everyone refuses to consider power cycling as part of normal operating procedure, then I think a lot of improvement is going to occur. However, if this industry explodes, there are going to be a lot of crappy products and consumers are going to lower their expectations, which isn't good for anybody. This is going to be a hot market, but right now I think there's a shortage of engineers who can really work in this domain, and that's probably holding the market back. This is probably good for long term product quality, but bad for someone like me who wants to stop working on defense systems and get into the commercial sector.

Note: This doesn't apply to low powered hardware, hard real time systems, one-of-a-kind systems, etc. Those are a whole different ballgame.

Re:Thanks to FS Developers

[gnalre]

I have to say that thats rubbish. It is only the recent trend that has blurred embedded OS with desktop OS which has produced this requirement. Vxworks for instance, which controls the majority of the market uses dosfs which does not seem to of affected its adoption.

What using linux as OS does mean is that you have a much larger choice on what you use. This can only be a good thing