Hacker News new | past | comments | ask | show | jobs | submit login

How do the projects being open source prevent something like ActiveX from coming to them?



It doesn't prevent a technology like ActiveX from coming to them, it prevents the CONSEQUENCES of such a technology had when it was in IE.


Ok, I still don't understand. I really got into web development around ten years ago, and have been a Firefox since back when Firefox was simply called Mozilla. So I have no experience, developer side or userland, with ActiveX. What were the consequences of ActiveX and how could open source have prevented it?


Well, ActiveX was a proprietary technology developed by Microsoft that only run on Windows, and especially only run on IE. So sites using it were only working with IE.

Webkit and Mozilla being open source means that no single company can control the projects or add a proprietary single-platform exception to them.

Now, a company could FORK Webkit/geecko and add something like ActiveX to it, but the fork wouldn't be part of webkit/geecko project anymore, and we'd still have webkit/geecko proper. For example, Google added NaCL which is something like ActiveX to Chrome, but not to Webkit itself.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: