Our great sponsors
-
-
-
SurveyJS
Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App. With SurveyJS form UI libraries, you can build and style forms in a fully-integrated drag & drop form builder, render them in your JS app, and store form submission data in any backend, inc. PHP, ASP.NET Core, and Node.js.
-
vscode-remote-release
Visual Studio Code Remote Development: Open any folder in WSL, in a Docker container, or on a remote machine using SSH and take advantage of VS Code's full feature set.
-
-
language-tools
🌐 Prisma Language Tools = Language Server and Prisma's VS Code extension. (by prisma)
-
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
VS Codium has tried, and not succeeded, to disable all telemetry[0][1]. This is with direct access to and patches to source code and all the knobs set to off.
If the direction of upstream is diametrically opposed to downstream, it is nearly impossible to prevent these issues.
[0] https://github.com/VSCodium/vscodium/issues/623
[1] https://github.com/VSCodium/vscodium/issues/631
JetBrains products have a perpetual fallback license so you absolutely can pay up front and then never pay again if you are ok being on an older version of the software.
Maybe you are the exception but I find that 99.99% of the people who use the "it's open source so I can modify it" argument never so much as look at the code let alone consider making modifications.
JetBrains products have an open-core (IntelliJ [0]) that can look at and contribute to if you so desire.
Lastly you say "None of these things are a big ask.", you just want the world on a silver platter for no cost, sorry but that is a big ask, especially if you care at all about the quality of your tools. If you're happy building an IDE from the group up using something like vscode and dealing with 100's of plugins that do the same thing slightly differently then be my guest but most of your arguments fall flat IMHO. Providing an excellent product with constant updates is not "rent-seeking".
[0] https://github.com/JetBrains/intellij-community
As a person who administers servers I absolutely HATE that vscode does this.
I don't know much about the specifics of remote deployment, but I feel like having vscode do this is just the wrong approach. I would say it probably needs to be some other CI/CD pipeline or something outside of the editor.
The problems I have is that every user gets like 1.5G of node junk stuffed in their home directory to support this. VScode spawns processes as the user that can't be controlled that can just kill servers (This is one bug I found, but there are issues with this that go much farther back than 2 years ago, https://github.com/microsoft/vscode-remote-release/issues/26...)
There doesn't seem to be any way to control this on the server side, so if I have users with the ability to write to their home directory, I cannot stop them from pushing this and potentially killing an instance.
It might be worth contacting these extensions' creators. If you already have the `.vsix` file for the VSCode marketplace, publishing to open-vsix is really super simple (create an account once, get a token, add a few lines to your publish script, e.g. https://github.com/prisma/language-tools/blob/94e4cd612d03ef...). Some just do not know about it.
For the atom case, it seems some users are going to continue to maintain it: https://github.com/atom-community/atom/
> Take the Jetbrains IDEs. I don't mean to offend any VSC fans out there but the Jetbrains IDEs are simply better and more mature in every single way.
I just discontinued my Jetbrains subscription after 10 years or so. Now I'm using VS Code and don't miss anything. My reasons for switching to VS Code are unrelated to the costs but purely due to quality issues and missing or poorly implemented features:
1. For all Jetbrains IDEs, ISO keyboard layout with dead keys doesn't work on Ubuntu based distros. I was baffled when I found out after saying goodbye to Windows lately. When filing a bug I was asked to wade through years old pages of comments to find somewhere someone who posted a workaround that was not compatible with the Toolbox. Well, at least the support could have sent me the instructions to fix it to save me spending an hour to read those threads at the Youtrack.
2. Vue 3 support was a disaster for itself. Still, Vue 3 support is very much behind the VS Code extension.
3. Same for Svelte. They are not even working on bugs / feature requests like intellisense in the templates.
4. Same for TailwindCSS. Never ending storing. Don't know and care if Jetbrains got it right by now.
5. Starting maybe 2 years ago, Jetbrains added feature for feature that were just distracting and annoying. This "run command in terminal" thingie for example. They're bloating their IDEs with new (mostly useless stuff) but don't fix essential bugs or get Webstorm back into shape.
6. Datagrip still doesn't (or maybe it does in the meantime) support SQLite STRICT TABLES (version 3.37). The simple answer from Jetbrains was: "The open source lib we're using does not support it so we don't." (Actually the lib (https://github.com/xerial/sqlite-jdbc) is currently unmaintained - another reason to be careful depending on a lib maintained by a single person.). The reply would be perfectly fine for an open source project, but not for a multi billion dollar company I as a customer had payed accumulated several thousand Euros in the last years.
I'm using mainly Go, Rust and several frontend frameworks. VS Code support for those is really good. Many things work much better in VS Code.
I just adapted the intellij-rust plugin from https://github.com/intellij-rust/intellij-rust to syntax highlight Rust slightly better. It works just fine, and I had to coordinate with nobody. Just edit file, build plugin, install plugin to the IDE (using the menu in the GUI interface). That's it.
Most of the stuff of Jetbrains is open source (under Apache Software License) and is available on github.
I know what you mean though: I would never again use a closed-source IDE, or a language with closed-source standard library. Microsoft Visual Studio made me learn that, decades ago.