Well, if people run WinDos for just that one bit of software, and MS continue to threaten to kill XP and force everyone to upgrade, why not let some people use WINE? At least that gets rid of one proprietary piece of software - the operating system.
In my own work I do my best to avoid M$ products - in all the planning meetings I've been to, any version of WinDos is seen as a threat from so many points of view that we'd rather spend more time and money doing without it. However, sometimes suppliers provide tools (such as specialised compilers for embedded systems) which only run on WinDos. If I had a year free I could get any number of free embedded compilers to do the job - but that's one job that's just a bit too big for my resources at the moment, so I must suffer the proprietary software + WINE. My next project involves using MS-XP-Embedded simply to get a product out within 2 years (using third party software). The development plan is to spend the next 2-3 years after that to rid the systems of XP-Embedded. After all, who knows how long MS will keep XP-E around? Of course I can only do this because all the managers are technical people - your typical pointy-haired boss will refuse to spend money on getting rid of XP-E because as far as they can see it works - why reduce the profits?
Bruce has got some good points, but he's being idealistic and ignoring much of reality (which I'm sure he is familiar with).
|