Linked by Thom Holwerda on Wed 29th Aug 2012 22:52 UTC
Linux Miguel de Icaza: "To sum up: (a) First dimension: things change too quickly, breaking both open source and proprietary software alike; (b) incompatibility across Linux distributions. This killed the ecosystem for third party developers trying to target Linux on the desktop. You would try once, do your best effort to support the 'top' distro or if you were feeling generous 'the top three' distros. Only to find out that your software no longer worked six months later. Supporting Linux on the desktop became a burden for independent developers." Mac OS X came along to scoop up the Linux defectors.
Permalink for comment 533417
To read all comments associated with this story, please click here.
RE[8]: Comment by woegjiub
by gilboa on Fri 31st Aug 2012 08:48 UTC in reply to "RE[7]: Comment by woegjiub"
gilboa
Member since:
2005-07-06

Try downloading a driver code from the Internet, compile for say, Windows 7 x86_64 or Windows 2K8 and install it and let me know how it goes. *

- Gilboa
* Hint: nothing. (As in driver-not-load-nothing)


Yet another hint: I was *not* referring to the download -> click -> click -> click -> reboot drivers installation process from the *user* perspective. I was referring to the *developer* perspective (those of you who missed the subject of this sub-thread, please feel free to re-read it).
In Linux, you simply post a tarball with a Makefile.
In Windows, especially in 64bit and especially once SecureBoot kicks in, developing and, God forbids, testing drivers is a *huge* hassle.

50% of the reason I rather stop porting my kernel code to Windows is the damn signature enforcement!

- Gilboa

Edited 2012-08-31 08:50 UTC

Reply Parent Score: 2