Whilst it's healthy to have competition, I'm not sure a rip-off of VS Code is in the spirit of open source. Did they try to work with the team at Microsoft to improve VS Code before forking it?
I'm extremely happy with its development, too; I think the team behind it has done as good a job as I have personally ever seen of both a.) delivering consistent improvements that excite the daily users, and b.) running an open source project.
Still, I absolutely think we are all better off with a vendor-nonspecific, open-source focused competitor.
I mean, once upon a time Microsoft Internet Explorer was the best browser for the Mac, too. There's probably enough awesome in the VS Code project to keep it from being corrupted by Microsoft's corporate priorities — and competition will help keep it that way, in addition to providing a possible alternative if that doesn't happen.
I bought it and gave it a whirl, but I went back.
Mainly because VS Code is much faster, and has a more normal UI (native open/save dialogs, way way better file browser, etc).
Also because the development velocity seems much faster. Every single VS Code major update has goodies in it that I personally want (plus blah blah whatever that I don't) and they come out once a month almost!
But I am curious (especially since I do still have the WebStorm license) what are some of the "IDE goodies" that give WebStorm the advantage in your view?
Everything I need is on Ctrl+p or Ctrl+shift+p.
vscode is like sublime to me, just seems the language completion got useful.
- It's not Theia versus VS Code
- Theia is not an "open-source alternative to VS Code"
- Theia is not a "rip-off of VS Code"
While confrontational narratives are appealing, it's more subtle than that: Theia is based on VS Code to address a different kind of need.
Much like TypeScript doesn't try to replace JavaScript, but builds on JS to address the need for type safety, Theia doesn't try to replace VS Code, but builds on VS Code to address the need for a framework to build IDEs for desktop (e.g. Arduino Pro, Arm mbed...) and for the cloud (e.g. Gitpod, Google Cloud Shell...).
As an open source project maintainer, I don't think it's necessary or easy to do that. Project teams and maintainers have different goals and sometimes it's much easier to fork and evolve without stepping on each other's toes. I'd even say that's the strength of open sourcing software under the right license.
VS Code is welcome to backport anything they like
They can't, as Theia contributors haven't necessarily signed the Microsoft CLA.
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.
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)
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.
For example I'm pretty sure Ford doesn't consult with Toyota before they introduce a new model.
If our working definition of rip-off is work alike that replicates the interface without sharing code, then I would say that open source has an incredibly long history of building through ripping off. Linux is a rip-off of MINIX is a rip-ff of Unix, GNU is a rip-off of Unix, various graphical interfaces over the years have been copies of commercial offerings. Copying VSC is absolutely in the spirit of Open Source.