News for hackers. Stuff that matters.
Re:If You’re Going To Kill It, Open Source It by ghaff on Thursday April 28, 2011 @07:10PM (#2495536)
One reason that "just open source it" isn't as easy as it sounds is that there tend to be a lot of IP restrictions, patenting and licensing encumbrances, NDAs, etc. that would take effort to identify much less resolve. When companies, like Sun, open sources various software, it took considerable effort to nail down all the problems and remove the parts that weren't there's to open source--which in the case of a device like a camera might well make the whole thing useless.
Re:If You’re Going To Kill It, Open Source It by bluespace on Thursday April 28, 2011 @09:01PM (#2495903)
Besides the legal side of things, the code might be being built with an company internal tool-chain, and comercial compilers, so it would be a bunch of work to even get it ready for a public release. All of this reinventing of the wheel probably limits nice fixes for common bugs over the years.
Re:If You’re Going To Kill It, Open Source It by zcid on Thursday April 28, 2011 @09:59PM (#2496055)
Compiler issues shouldn't hold you back. Release it anyway. If someone is interested enough, they will more than likely be willing to work with what they can get. Let the burden of correcting the code fall on them.
Re:If You’re Going To Kill It, Open Source It by bluespace on Thursday April 28, 2011 @10:52PM (#2496163)
While that sounds good in theory, when customers are involved, you want to make sure that you have your best foot forward. So filling up forums with complaints is never a good thing.
Re:If You’re Going To Kill It, Open Source It by hollerith on Thursday April 28, 2011 @10:07PM (#2496067)
Which suggests that working on open-source compilers tends to support the open-source ecosystem more than working on end-user apps.
Re:If You’re Going To Kill It, Open Source It by nitrogen on Friday April 29, 2011 @01:51AM (#2496506)
I'm guessing that failed startups don't release their code because their investors see it as an asset to be liquidated to recover some of the investment. Can anybody with failed startup experience comment on this possibility?
Re:If You’re Going To Kill It, Open Source It by bruce511 on Friday April 29, 2011 @06:44AM (#2496955)
Technically the source code is an asset - so the company may be limited in terms of what they can do.

For example, a company that closed while owing money could not just "distribute" their remaining assets by releasing them into the open-source domain. Investors, employees, shareholders even founders may have legitimate claims to maximizing the value of that asset.

Equally, if there are multiple parts to the asset, they may not necessarily be disposed of "together". As a simplistic example a robotics company may sell off the hardware separate to software. And the software itself might be separated into different lots.

So the _creators_ of the product are not necessarily the _disposers_ of the product. And the person buying the thing (for whatever reason) is unlikely to spend money and then just give it away.

For companies that remain existing after the discontinuation of the product, the problems are even more complex. Take for example Sony's robotic technology. Just because they've discontinued the consumer products does not mean their investment in the tech is wasted. I think it's safe to assume that at some point in the future Sony would be able to either sell, or leverage that investment.

At the end of the day it's about balancing the upside and the downside. The upside to Sony, HP etc is negligible (some hacker types are happy) whereas the potential downside (loss of IP rights, effort to release, on-going impact, legal liability, trademark issues etc) are substantial. Even the effort to determine the downside is significant.

Now of course, if you've got some unheard of webapp, that attracted 5 users before you killed it, it's trivial to open-source that. On the other hand that _is_ probably happening all the time, and nobody cares.