5 ms·
One could argue if VScode is an open source project or not. But when copying an open source project, it's not called rip-off, it's called fork. The intentions o
by z3t4 7y ago
One could argue if VScode is an open source project or not. But when copying an open source project, it's not called rip-off, it's called fork. The intentions of forks are to improve the software, try out new ideas, etc, and the original software can merge new features developed in the fork. Forks can however be "hostile" when the intentions are to rip-off the original creator by stealing users/sponsors and making the fork proprietary, which is a strategy used by some cough software businesses.
- GordonS 7y ago> One could argue if VScode is an open source project or not I mean... not really, no?! It's MIT licensed and fits any definition of OSS I've ever seen. AFAIK, the only non-OSS part is the installer.
- z3t4 7y agoOne problem is that you are required to sign away your rights in order to contribute, so that in the future you might not have the rights to use your own work. Then there are proprietary extensions, like the "remote" extension (1) that competes with Theia's open source solution. Also see open source vs FOSS (2) 1) https://news.ycombinator.com/item?id=22792612 https://news.ycombinator.com/item?id=22792612 2) http://wiki.c2.com/?FreeAsInBeer http://wiki.c2.com/?FreeAsInBeer
- GordonS 7y agoI've well aware of the OSS/FOSS definitions - it was exactly those that made me question your argument thst VS Code isn't open source. It plainly is, and indeed is Free As In Beer. I don't see the problem with proprietary extensions - any open plugin mechanism will have at least some proprietary extensions (by the primary maintainer, or by third parties), including Theia's if it gains enough traction.
- jhasse 7y agoWhile it is also available under the MIT license, MS reserves the right to re-license it however they see fit. If you want to contribute, you'll have to sign their CLA to give Microsoft that right.