Linked by Thom Holwerda on Wed 29th Aug 2012 22:52 UTC
Permalink for comment 533417
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
Features
Linked by Thom Holwerda on 06/13/13 14:35 UTC
Linked by Thom Holwerda on 06/11/13 17:07 UTC
Linked by Thom Holwerda on 06/10/13 23:13 UTC
Linked by Thom Holwerda on 06/08/13 14:57 UTC
Linked by Thom Holwerda on 06/07/13 11:40 UTC
Linked by Thom Holwerda on 06/04/13 12:45 UTC
Linked by nfeske on 05/31/13 10:12 UTC
Linked by Thom Holwerda on 05/29/13 16:59 UTC
Linked by Thom Holwerda on 05/24/13 17:26 UTC
Linked by Thom Holwerda on 05/21/13 21:38 UTC
More Features »
Sponsored Links



Member since:
2005-07-06
- 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