To view parent comment, click here.
To read all comments associated with this story, please click here.
It's not stupid at all. Fixing an in-tree driver in Linux involves a submission/approval process and then you have to wait for the distros to pick up the change. A simple bit flip can take months to get to users.
In Windows you can fix a driver and then immediately publish to the web server. You can in fact automate the entire process with a single click. "
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)
Edited 2012-08-30 14:29 UTC
Why bother? The .exe works fine so no compiling. I know its shocking, not needing to compile everything, but it does have its advantages.
For example my 73 year old dad got impatient because I couldn't come out and install Win 7 on that new machine i built him until the weekend. he decided to DIY and when i got there I thought I'd have a mess, turned out all I needed to do was show him how to install his browser. All the drivers, patches, updates, and even the AV (it popped up a little box on first boot and gave him the choice of several free or pay AVs, he chose MSE which works fine) was all taken care of, he just didn't know where to download his browser from.
Like it or not, admit it or not, Linux is a geeker OS that is a PITA for your average user. Sure if you know compiler flags, can google for fixes, know your way around the forums, then you'll have no problems. lets see, that covers....about 0.97% of the public according to netstats. The rest? Sorry but your OS just don't cut it.
Don't use Windows, but in my experience, all you have to do is download the driver (For recent hardware, there will be 4 version of the driver - XP, Vista, Windows 7 and soon to be Windows 8).
The drivers will come in a single executable package. Bingo.
With Linux, unless you are using NVidia, it might involve tarballs (you have lost 99% of potential users right there), or hunting down a distribution specific packaged binary.
- 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
You have to use the signature override
http://www.ngohq.com/home.php?page=dseo
A fair point but not a big deal





Member since:
2012-06-22
It's not stupid at all. Fixing an in-tree driver in Linux involves a submission/approval process and then you have to wait for the distros to pick up the change. A simple bit flip can take months to get to users.
In Windows you can fix a driver and then immediately publish to the web server. You can in fact automate the entire process with a single click.