Linked by Thom Holwerda on Fri 15th Jan 2010 23:06 UTC
Thread beginning with comment 404555
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
RE: Linux vs Windows dev platform
by nt_jerkface on Mon 18th Jan 2010 05:43
in reply to "Linux vs Windows dev platform"
Ed W. Cogburn mostly nailed it when he said that it is mostly about the market share.
Companies will endure a lot of API annoyances and subcomponent churn if the market is worth it.
Companies will endure a lot of API annoyances and subcomponent churn if the market is worth it.
So how do you build your market with an unstable platform?
Several remarks about Linux component changes seem to imply that Windows is not having it's own comparable changes. That is silly.
I've lost count of the number of database interfaces MS published
Cue talk about Windows breaking interfaces between decades while trying to ignore the fact that Linux does it annually.
Going by history you can build a sound app in Windows and expect it to work for the life of the OS.
With Ubuntu you can't even expect it to work for a year.
They say that the definition of insanity is doing the same thing while expecting different results and that seems to describe the state of the Linux desktop. People 10 years ago were saying that broken APIs were no big deal and that Linux would gain share anyways. It didn't gain share, it's still at 1%.




Member since:
2009-09-09
Ed W. Cogburn mostly nailed it when he said that it is mostly about the market share.
Companies will endure a lot of API annoyances and subcomponent churn if the market is worth it.
Several remarks about Linux component changes seem to imply that Windows is not having it's own comparable changes. That is silly.
I've lost count of the number of database interfaces MS published. Sound system, video, messaging - they all changed over the last decade - sometimes several times.
Sure - old APIs tend to stay around - but there's plenty of *2 or *Ex versions. And that's just win32. Of course now it's often .Net (and don't think you can get rid of 1.1 just because 3.x is out). In between it was first DDE and then COM.
Technology advances. Demands change. People learn what they should have done differently. The platform adapts. It happens to both Windows and Linux. It would be crazy to keep HAL if a better replacement can be done.
If there is a viable market - companies will deal with the hurdles of targeting the platform.
And a typical program doesn't have to worry about OS internals about what hardware is un/mounted and when - that's what the OS is for. The program opens a file - it doesn't usually care about the details of that file being available there. Stuff like mouse movement, button clicks and other such hardware are dealt with by DE platform libs. Most of which don't change all the time. And the change that happens, happens on all platforms.