4 ms·
I don't think your argument works. The license is not relevant.. you need an API layer that allow customization via OS hooks, drivers and apps. Also, even if yo
by la_barba 7y ago
I don't think your argument works. The license is not relevant.. you need an API layer that allow customization via OS hooks, drivers and apps. Also, even if you had a closed source license, there is no reason you cannot share it with your partners.
- erikpukinskis 7y agoIn a perfect world, with nice roadmaps and planning and easy negotiations, yes Microsoft will develop hooks for you. In the world where you have two months to get some ridiculous feature out because your competitor announced they’re doing it, it helps to just have the source code and throw engineers at the problem.
- la_barba 7y ago>In a perfect world, with nice roadmaps and planning and easy negotiations, yes Microsoft will develop hooks for you. I don't why you think this is some pie in the sky fantasy. What I said is _already_ happening. This is normal stuff. For e.g. https://www.microsoft.com/en-us/sharedsource/ https://www.microsoft.com/en-us/sharedsource/ Or specifically - https://www.microsoft.com/en-us/sharedsource/windows-embedded-ce-licensing-program.aspx https://www.microsoft.com/en-us/sharedsource/windows-embedde...
- erikpukinskis 7y agoSure, it does happen. The question is whether it happens frequently enough to satisfy OEMs desires for how often they want new API and how fast that API materializes. And just having the source isn’t really enough. There are no StackOverflow articles on how to work with MS shared source code. You’re thinking about best case scenarios, but markets move based on median case.
- la_barba 7y ago>You’re thinking about best case scenarios, but markets move based on median case. I gave you data and evidence. Its your call if you want to continue dealing with hypotheticals.