Skip to content

Comment on Google Adds 'Kodi' to Autocomplete Piracy Filterparent

Comments

The company I work for creates STB software, and while we do use a large number of open source components the message from above is to avoid GPL where possible. Any use of GPLv2 must be signed off after review, GPLv3 is simply banned.

Unfortunately most companies in the sector, from hardware manufacturers to integrators, have equivalent, if not worse open-source policies. They are willing to take the hard work of others where it will accelerate development, but view sharing back as a loss of control and competitive advantage.

This is in part due to pressure from operators and content providers, who are very fearful of losing control over distribution and tend to view anything open with deep suspicion.

but view sharing back as a loss of control and competitive advantage.

I’ve never understood this mentality (disclaimer: I’ve worked on set top box software). The competitive concern would only be valid if the company’s closed source software was any good. Every closed source set top box software I’ve ever seen was beyond awful, at least compared to open source alternatives. Who on earth would gain any competitive advantage from even looking at the code, let alone using it in a competing product?

AboutSource Built by g1lg1l

Hackerly is an independent reader for Hacker News, built on the public HN API. Not affiliated with Y Combinator.