3 ms·
I'll never understand selecting windows for any embedded system that is expected to have a 10+ year life. If you look at their history, they frequently blow up
by dv_dt 8y ago
I'll never understand selecting windows for any embedded system that is expected to have a 10+ year life. If you look at their history, they frequently blow up the development environment every 5-6(?) years. Yes they'll provide support, but it comes at being increasingly held hostage to whatever level of long term support costs are in vogue at the time. For a 20-30 year support life, that's a guaranteed headache.
- snowwindwaves 8y agoYou don't install any updates or change anything once the machine is setup and performing its duty. If the hardware fails you replace it with similar hardware and install the original software from CD again. I see windows NT on ships, windows 2000 in power stations, etc.
- dv_dt 8y agoWeren't failing legacy computers on bridge systems one of the contributors to the Navy destroyer crashes?
- snowwindwaves 8y agoImproper maintenance of worn out components can cause a failure resulting in a crash, be they computer components, electrical components, or mechanical components.
- tsukikage 8y agoLinux doesn't necessarily help here. Ubuntu LTS lifetime is 3-5 years, others are similar; outside this, distro maintainers think nothing of just dropping packages from the distro that the deployment may be relying on, so upgrading is not simple.
- cesarb 8y agoThe difference is that with Linux you can self-support, or pay for someone else to do it, since the whole source code is available to everyone and the licence allows it. Also, a better comparison would be with RHEL, which has a lifetime of 10 years or more.