>> I've seem my share of "embedded" devices (signage, control-room-displays) where the vendor just slapped their proprietary .exe in Autostart and left the Vendor supplied Win-XP + Nagware + never-updated-virus-scanner + ... intact.
This is what scares me. This happens so often and so frequent. I know it may be a shock to HN, but huge amounts of "embedded devices" are built this way. I for one would love to see custom tailored Android or linux -- but I'll say it again -- I really really do not trust them to do it right. Sorry to start the day pessimistically. :)
Why not? You pay a one-time, small license fee, you get years of free support from a major company, I don't have to document all the details of my stripped down kernel and how to recreate it, you can hire anybody off the street to work on it long after I am gone (and I am long gone from that company, but the hardware lives on), they didn't have to pay me to build out a unique OS, the low power computer we had could more than handle XP, there was (and continues to be) continued new, unknown requirements and upgrades, the people required to occasionally touch the interface had more PC experience than for any embedded or linux OS, and on and on.
Why wouldn't I slap a copy of XP on there? Well, this story is the counter-argument, of course. I still think it was the right decision.
In either case, I don't understand why ATM industry should be pissed - it's not that they were patching ATMs on a regular basis... In case of XP Embedded the patching story is even more convoluted.
The WinXP users are in the same boat as the Ubuntu users - someone is going to need to update that video driver and smooth that new software into the production run without tanking machines that are already out there. Service techs HATE having to deal with 24 different flavors of the same circuit board and crossing their fingers they updated the right file onto the correct board.
So yeah it's lazy that relying on Windows to handle all that lifting but, hey guess what, there's a lot better chance someone has a Windows driver for that new display that the Ubuntu crowd does.
Android has a lot of potential for embedded GUI usage (I'm doing it myself) but the driver stack integration is a LOT tighter than slapping another DLL into the mix.
Also, I didn't get your remark about "8 year old Ubuntu". Why not a newer QT based Ubuntu?
And currently it's pretty easy to do this, with build-scripts and infrastructure in place. Maybe even using a tailored Android?
But then I somehow doubt that the industry would take that opportunity: I've seem my share of "embedded" devices (signage, control-room-displays) where the vendor just slapped their proprietary .exe in Autostart and left the Vendor supplied Win-XP + Nagware + never-updated-virus-scanner + ... intact.
Why? Because people in industry are lazy (they should be, maximizing their ROI, doing as little own work), and so going the same route, but with an 8 year old Ubuntu will not gain anything.