3 ms·
I wonder - would it be a good idea to release the source code a few versions old? Competitors likely already have implemented similar things so no major corpora
by user_7832 5y ago
I wonder - would it be a good idea to release the source code a few versions old? Competitors likely already have implemented similar things so no major corporate issues. Not open source, just source-available, so no issue with Amazon running off with the code. And power users/fans can add their own additional software which likely will still work with newer versions.
Of course, I'm likely missing several things - I'd be grateful if someone could point these out. (I've been thinking of this strategy not just in this specific case but in general.)
- soapdog 5y agoWell, for one thing you might be missing is that software doesn't change drastically between versions these days. Specially if you factor rapid release cycles in. So whatever is present in your new version is just a small set of features compared to all that is available on your older versions. People might simply be tempted by the FOSS version, not because it is FOSS but because it is free. A ton of people use FOSS software not because of all the ethos of free software but because it is gratis. If an old version is already useful enough and available as a fork, it will be hard to tempt some one to pay for your full version.
- user_7832 5y agoYeah I get your point. I was not referring to one numerical version behind but rather one "version with significant features" behind, sorry should have been more clear. The cost point is very valid. Of course if I were to put out any code (I'm not a full-time developer) it would be as a hobby so monetization would be a bonus. I wonder if Kreya/others etc could offer some customer service that's so much of a benefit that corps want it (maybe like what Red Hat does). Though that'll also add complexity... a chicken and egg problem I suppose.