4 ms·
I wouldn't be so positive about open-source everywhere. I'd recommend keeping some amount of the server-side closed source. The risk I see is that competitors c
by barrkel 16y ago
I wouldn't be so positive about open-source everywhere. I'd recommend keeping some amount of the server-side closed source. The risk I see is that competitors can simply use your code and run the cheapest hardware they can find, while you have to run the cheapest hardware you can find and maintain and improve the software. Unless you have a different edge on the hardware side, you have no sustainable competitive advantage.
So I'd suggest you stick with the open API, and perhaps have an open reference implementation, but add value in a secret sauce on the server side which competitors can't simply copy.
- nollidge 16y agoSurely they've already thought of this.
- barrkel 16y agoAnd I would expect my comment to elicit their thinking. From the post, it seems a little pollyannaish, paraphrasing: open source for the hackers, charging money from the start for the business, everybody wins, yay! On the other hand, perhaps their thinking on this is part of the secret sauce, and it's being kept secret for good reason.
- deleted 16y ago[deleted]
- thaumaturgy 16y ago> Linode could offer this stack as an in browser way to access lish. Linode already has an in-browser interface to Lish, and I don't think Lish would work over VNC anyway, since it seems to operate on a lower level.
- theBobMcCormick 16y agoOpen Source could be an advantage for them if they change their license to the AGPLv3. With an AGPLv3 license, any competitors would be required to make their modifications available for download. But as the copyright holder, the OP would not have to release any source he didn't want to, giving him the flexibility to run private, closed source extensions/enhancements if he chooses.
- bretthoerner 16y agoKeeping in mind that he can't make use of any competitors' (or even friendly open source contributors') patches because they will be licensed under the AGPLv3 and not under his copyright. I guess they could sign the copyright over to him, but I don't see another way around that. (IANAL)
- runT1ME 16y agoDon't a lot of Open Source companies make you sign copyright over? Or is that not the case. How did MySql handle this since they were dual licensed?
- bretthoerner 16y agoYou only have to sign it over if you want it in the official distribution, which I suppose most normal contributors do. But if someone (competitor or not) forks and adds SuperAwesomeFeature (without signing the copyright over), pkrumins can't pull that into his and license it commercially. It'd have to only exist in his AGPLv3 version, which sounds like hell.
- runT1ME 16y agoSounds like a problem with any OS license, not just AGPL...
- bretthoerner 16y agoAny GPL-like license, yes. But people like to bring up the AGPL because it means "Muhahaha, if they ever run it as a service over the net it means they have to share their source!" as if it has any benefit to their commercial product.
- runT1ME 16y agoThis is an interesting thought exercise. I'm going to postulate that there is a benefit of the AGPL. Lets take a look at a company like JBoss, who may have benefited from the AGPL opposed to the LGPL they use. A company who wanted to use their products for commercial use must provide a link somewhere on their page to the source, and share any mods. I think this is a big incentive to buy a commerical license from them, as it may look a little less than professional. Assuming they don't though, and they publish their changes, there is still incentive for them to sign over the copywrite. If they want any backwards compatibility for updates and bug fixes (very important for a runtime platform), they need to. Its that or port everything back over.
- Goosey 16y agoIt's fine; the source code to their product is not a competitive advantage ( http://blog.asmartbear.com/unfair-advantages.html http://blog.asmartbear.com/unfair-advantages.html )
- thaumaturgy 16y agoThat's absurd.
- barrkel 16y agoCopying something done well isn't as easy as it looks, cf. Google, iPhone, MS Office, etc.