|
|
|
|
|
by Pet_Ant
797 days ago
|
|
> Don't use OSI open-source unless it's entirely a labor of love that you're giving away free. Well, know what your secret sauce is. I think performance is really the best differentiator. Make a fully behaviourally compatible (maybe not bug for bug) version available and then sell a proprietary faster version. Think an compiler that doesn't due any optimisation and outputs naive code. You know have a useful OSI project, and a clear value add, and a clear boundary between the two. This is really applicable for databases, and it still leaves you with something useful for learning small projects, and for developers to run locally on their own machines. |
|
I don't understand this at all. Most open source projects start out equally as a means to give back to and collaborate with the community as well as showcase one's skills. You're asking me to purposefully publish badly optimized software? I don't have it in me. That offends my sensibilities of craftsmanship. A 'slow' open source project will never get traction. Even if it did, I also don't know how an open source project wouldn't immediately have it's obvious performance bottlenecks fixed.
Far better to go the VSCode route. Release a useful project, then release paid extensions for it.