On a surface level, this is true. Vast majority of the code that makes VS Code is MIT licensed.
But the configuration of what marketplace is used and what extensions have access to the privileged "proposed API" makes huge difference in what Microsoft/GitHub can provide as user experience and what other developers can do.
I understand the difference in UX but I'm really not concerned with that. The code itself is all open source for the VSCode client and will probably remain that way. Extensions like Pylance are replaceable and the Python extension can already just use Jedi instead. Also I'm sorry but that article is really terrible in terms of both content and layout. In terms of content, its only real argument is the .Net fiasco and some issue with Gitpod that really doesn't matter. In terms of content, the page is utterly unreadable
I'm perfectly aware of what Microsoft could do in some distant future. But as is, for all intents and purposes, VSCode is open source
> But as is, for all intents and purposes, VSCode is open source
... Except that if you use the source to make your own build, you lose the extension ecosystem that is one of VSC's major selling points. It is at best a worked example of tivoization.
You can easily just download the extension dist files and dump it in the extensions folder. Most extensions are open source too and VScode is not doing anything special with the extension files. They're mostly just JS. You lose out on the convenience of the marketplace but the open source version exists. If a maintainer doesn't have their extension on there, usually reaching out to them will have them upload it there too or as I mentioned, just clone the repo
I'd recommend looking into Logseq[0], it's free and open source and stores all notes on disk as Markdown. I version my notes with Git, but Syncthing will also work.
It does, but if you use the build in synchronization, your notes will by synchronized as (optionally encrypted) files. I think using syncthing would be possible if you make Joplin synchronize to a local directory, and use syncthing to sync that directory.
I used to use Logseq with Syncthing, but I ran into a bunch of sync conflicts that were annoying to deal with and sometimes it would just stop syncing for no reason. Luckily, they've just made Logseq Sync available to all backers on OpenCollective and it works quite well. I'm very happy with the setup now. I think they're making Sync available as a paid monthly service soon.
Isn't this like saying you need your own slack instance for your team? It should be IMO possible to limit conversation on mastodon to a group of people as an alternative to limiting it to an instance.
I've read somewhere that Starlink has the potential of replacing private optic cable connections between world stock exchanges, providing its customers (read micro trading companies) latency advantage.