3 ms·
My gut feeling says "Don't do that, it won't work." Doing an "open core" approach can work (although to be honest, I'm not fan), but it's one thing to have a p
by mindcrime 12y ago
My gut feeling says "Don't do that, it won't work." Doing an "open core" approach can work (although to be honest, I'm not fan), but it's one thing to have a paid version that adds real value on top of the open source version. But when the only difference between the two versions is that one is intentionally "hobbled"? I don't think developers are going to go for that. I know I wouldn't. To be honest, it sounds and feels like the kind of thing I'd expect from Microsoft or CA.
I'd say just go with a proprietary library across the board, or a completely open source library, and not try to be both.
- dougk16 12y agoAgree with all of what you said and thanks for responding. The hobbling I have in mind is targeted such that it wouldn't practically impact users that probably wouldn't pay anyway (class projects, hobby projects, etc.). I'm probably not getting that point across clearly and my actual situation would take some time to explain. Overall this is more a thought experiment than something I'm actively considering though. The more realistic approach I'm going to take is either open core or dual license.