3 ms·
The most obvious benefit would be adding similar functionality to other IDEs. But really, why assume that you can guess what the benefit would be? Open the code
by int_19h 8y ago
The most obvious benefit would be adding similar functionality to other IDEs. But really, why assume that you can guess what the benefit would be? Open the code and let the community decide what it can do with it. It doesn't have to come together with an open development process, necessarily.
Some other generic benefits that would apply here are the ability to debug issues, and interop/compatibility. The first one is often dismissed on the grounds that most users are unable to do this; but we're talking about dev tooling here, where the target audience has the necessary skills. From my own experience working on open source dev tools, this is probably the biggest benefit - not PRs, but detailed bug reports that already mostly narrow down the problem. In cases where the original bug can be very environment-specific or otherwise hard to repro, this can make the difference between resolved and closed as no-repro.
Interop/compatibility is also an important angle, and very hard to predict in advance. But any extension that interacts with this one, or is used by it, could potentially benefit. This also ties into the ability to debug it somewhat - if extension A breaks extension B, it's much easier for the author of A to figure out why, exactly, and what's the best way to avoid it, if they have the source for B.
Then there's the ethical angle. VSCode itself is open source. So far as I know, all extensions that this one relies on to enable various customer scenarios - e.g. IDE support for various GCP-supported languages - are open source. For something that derives a substantial (arguably, the majority) of its value from those, closing the source runs counter to the spirit of the whole thing, regardless of the license terms. I can understand doing so for some specific business reasons - e.g. use of some proprietary components, or trade secrets in the code - but if it's only a question of not wanting to make the extra effort, it's kinda disrespectful towards people who did make that effort. Even that would be understandable if we were talking about a non-profit project that has limited resources and has to ration them. But this is Google, and the product itself is a part of the subscription-driven GCP ecosystem.
In general, the reason why open source is so widespread today is because for-profit corporations subsidize a lot of it. They have their own non-altruistic reasons, of course, but the entire arrangement is beneficial to all. So it's a commons, and we should all strive to maintain it and the cultural norms that make it sustainable.
(Full disclosure: I am a developer working on one of the relevant Microsoft VSCode extensions. Everything I write here is strictly my personal opinion. I do not speak in any official capacity.)
- DannyBee 8y ago"It doesn't have to come together with an open development process, necessarily." I think the amount people agree with this varies wildly. There are plenty of people who consider it an attractive nuisance if it doesn't. You don't have to look very hard in hacker news threads to find google/MS/etc getting blamed for occupying a space by doing this. I really don't think you want to push the ethical angle - vscode was definitely not open sourced for ethical reasons as part of some grand altruistic gesture and to push forward a great ethos. I was told that directly by the people who started it and made those decisions. That isn't a statement that it was a secret evil scheme (it certainly wasn't), but those were just ancillary benefits, not the main goal. I will leave alone the fact that your argument does not seem to have convinced MS in a number of places where there is no perceivable user benefit (see, e.g., the C++ extension) and it runs directly contrary to your claims, since you want to speak in a non-official capacity :) Bottom line: I think this is a fairly simplistic view of the tradeoffs. I'm certainly not exactly elucidating it in huge detail, but that's because i'm surprised people want to believe these are fairly simple issues amenable to a few paragraphs of analysis.
- int_19h 8y agoTo clarify, my point isn't "open source good, closed source bad", nor that things get open sourced primarily for ethical reasons. With copyleft, the basic principle wrt code reuse and sharing is "take what you need, contribute back the value added", and it is encoded in the license itself. With non-copyleft licenses like MIT, the only thing that's encoded is "take what you need" - but I would argue that there's also an implied "... contribute back what you can", that is broadly respected in practice, and is an important part of what makes the model sustainable. I remember what the industry was like when the biggest bar to shipping open source in for-profit environments was the default attitude of "why even bother?", and in practice that meant a lot less of it all around, even where not having the code made life much more difficult for others. This attitude took a lot of collective time and effort across the entire industry to change, in many cases by individual employees inside those FOSS-hostile environments actively working towards that goal for altruistic reasons. In the end, I think we're all better off for it - individual devs and companies alike - and should strive to maintain those gains, and the culture that enables them. Arguing for closed source by default is contrary to that, in my opinion. Closed source itself is not.