"First they ignore you, then they laugh at you, then they fight you, then you win." -Gandhi
why this quote got down voted? it's exactly how Opensource progresses.
The Windows Driver Frameworks are on GitHub
41–50 of 87 posts
Re: The Windows Driver Frameworks are on GitHub
#42Earlier quoted context omitted.
I like both eco-systems a lot, however Java is currently more open than .NET, specially if you look around for available certified JVMs.
In this particular case, i'd prefer Windows above Oracle (Java) anytime, considering they deliver malware with their Java Setup... Edit: Some people give a link to an alterantive download without malware... You know 99% of all Java downloads don't know that, do you?
i just don't install programs that include malware. i can do without it. in all cases, i can get around it. i don't care enough to.
i use 0 programs made in java on my desktop/laptop. it makes sense on a server, it doesn't belong on the desktop, the malware is just another reason.
Re: The Windows Driver Frameworks are on GitHub
#43What effect will this have on the ability to boost driver support in Linux, if any? FreeBSD has ndisgen [1], but would this help improve that or a broader set of driver use in Linux? Secondly, what about WINE? [1]: https://www.freebsd.org/cgi/man.cgi?query=ndisgen
It means nothing. WDF is a high-level framework for drivers on top of Windows NT – basically a convenience library you link with. While using WDF, you can freely call regular NT functions too. It's like MFC to Win32.
Thanks for the information. I'm not at all involved in driver work so I have no clue. :)
Re: The Windows Driver Frameworks are on GitHub
#44One barrier to developing drivers for Windows is the driver signing policy https://msdn.microsoft.com/en-us/library/windows/hardware/ff... which requires you to pay for a software publisher certificate.
I used my Authenticode cert for this, it wasn't very expensive.
How much out of interest? I see prices of 180 USD a year on Google search. It's not expensive but for say an open source project which might not be bringing in income it's an annoying cost.
Re: The Windows Driver Frameworks are on GitHub
#45"we understand there’s no substitute for having OS source available" Ho ho ho.
Re: The Windows Driver Frameworks are on GitHub
#46[deleted]
Let me see if I have this straight: - Keeps source closed. Is therefore evil. - Opens source. Must be up to no good, because is evil. This might qualify for the original meaning of, begging the question...
They're considered evil not because they kept source closed, but because they actively abused their monopoly to illegally malign their competition. That's what the problem with EEE is.
They're open-sourcing stuff (which will in theory make it harder for them to do it in the future), but that doesn't mean they've repented and have good intentions. They're open-sourcing their software purely out of self-interest, and people are wondering what exactly this self-interest is, and are being quite reasonably cautious.
Re: The Windows Driver Frameworks are on GitHub
#47Earlier quoted context omitted.
I used my Authenticode cert for this, it wasn't very expensive.
How much out of interest? I see prices of 180 USD a year on Google search. It's not expensive but for say an open source project which might not be bringing in income it's an annoying cost.
You also have to pay for each signature ($100 I think, not really sure). And the certification process is anything but easy (though it depends on the type of the driver).
Re: The Windows Driver Frameworks are on GitHub
#48Earlier quoted context omitted.
Drivers aren't much of a threat to the Windows hegemony because since Vista they've needed to be signed. If you don't mind taking the risk of running with driver signature verification turned off you can get FSDs for XFS and Ext4.
Last time I checked, code signing certificates could be had for $400 a year, not an exorbitant price to many tech enthusiasts.
However, being able to support the driver so it passes the certification process with every update is not something many tech enthusiasts would want to do.
Re: The Windows Driver Frameworks are on GitHub
#49There are actually some strong OS voices in Microsoft. I was at Solutions Linux in France (around 2006 iirc) and there was a Microsoft booth. Since our booth had some downtime I talked to the guy manning their booth who was kind of stranded between Linux distros and FLOSS companies. He was pretty cool and genuinely trying to advance OS within Microsoft but said it's a pretty frustrating experience overall (his descri…
Scott Hanselman has been talking about the process of changing Microsoft's culture toward open source on Hanselminutes since he started working there about five years (and a couple of hundred episodes) ago.
The move to open source has been in the works a long time and appears (to me at least) as part of Ballmer and Gates long term strategic plan for the era when they were no longer the largest and second largest shareholders and the company was more beholden to Wall Street.
The new post-founder (ok Ballmer wasn't technically a founder) era at Microsoft has been set up so that Microsoft can operate like a software company again. That means embracing current industry culture. Practices that made sense when software came in boxes and was sold through magazines and connecting meant squawking over POTS, needed to be looked at with an eye toward long term.
Nadella was set up by Ballmer to fall into the pit of success. The super tanker's rudder was changed years ago. The move toward open source is no more overnight than the hardware build quality of the surface.
Re: The Windows Driver Frameworks are on GitHub
#50Earlier quoted context omitted.
How much out of interest? I see prices of 180 USD a year on Google search. It's not expensive but for say an open source project which might not be bringing in income it's an annoying cost.
You also have to pay for each signature ($100 I think, not really sure). And the certification process is anything but easy (though it depends on the type of the driver).
Driver signing and WHQL are two completely different things and are NOT related. Your SIGNED driver does NOT need to be WHQL certified.