Live data from Hacker News

If You’re Going To Kill It, Open Source It

blog.makezine.com

11–20 of 42 posts

Re: If You’re Going To Kill It, Open Source It

#11
post #7

The AIBO used a proprietary commercial operating system and required a separate set of commercial compilers to produce valid code. When I was working on it through a special arrangement with Sony Research, I made a bunch of perl scripts that could munge the assembly generated from gcc so that the assembler could generate code that worked properly on the robots, but there were still a large number of very expensive co…

[deleted]

Re: If You’re Going To Kill It, Open Source It

#13
post #2

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 devic…

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

#14
post #10
post #7

The AIBO used a proprietary commercial operating system and required a separate set of commercial compilers to produce valid code. When I was working on it through a special arrangement with Sony Research, I made a bunch of perl scripts that could munge the assembly generated from gcc so that the assembler could generate code that worked properly on the robots, but there were still a large number of very expensive co…

That's interesting, and your Perl scripts sound like the sort of thing I would utterly fail at were I to attempt to create them. What about the hardware of the robots though? Would all of the various interesting parts be covered by patents, etc., and thus be unsuitable for opening up? (Sorry if my questions tread on NDA territory - that's one long-lived NDA.)

Not at all! It wasn't that bad -- the object files just needed to have sections that had particular size restrictions, names, etc. Nothing too tricky.

I don't recall the hardware being too separately encumbered. Sony Research provided all of the early adopters with significant technical specifications about the hardware itself, though admittedly much of it was documented in Japanese and this is ~10 years before google translate. I remember one other independent research group rewrote all of Sony's dynamic stability code and was able to increase walking speed significantly, and there was a lot of that level of information available.

Re: If You’re Going To Kill It, Open Source It

#15
post #2

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 devic…

[deleted]

Re: If You’re Going To Kill It, Open Source It

#16
post #5

There are three reasons why organizations and people don't open source their failed projects. * Intellectual property issues * Pride * Pride Don't underestimate the power of emotion, especially when it involves failure.

The last two go for communities, too. I've been a member of at least a couple great online communities where the owners lost interest but could not handle handing their baby to someone else - so they killed them instead.

They seemed utterly blind to the awesome communities that had formed, and unable to grasp how much harm shutting down caused to so many people.

Re: If You’re Going To Kill It, Open Source It

#18
post #2

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 devic…

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.

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

#19
post #2

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 devic…

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.

Which suggests that working on open-source compilers tends to support the open-source ecosystem more than working on end-user apps.
Post reply on HN