4 ms·
At the risk of destroying their reputation. If you have an open source version and a closed source version, it's better to differentiate them on features and su
by olefoo 16y ago
At the risk of destroying their reputation. If you have an open source version and a closed source version, it's better to differentiate them on features and support not on code quality. If someone has their technical staff do a code audit and the answer comes back that this code is so horrible that we don't want it touching our data, that will be thought true of both versions.
- amichail 16y agoEveryone would know that bugs have been inserted into the code to make it unusable. But programmers can still learn something from the code regardless (e.g., high level design).