See also #28

The project is called VSCodium because the originating repo is called vscode. With recent updates, the binary itself is called codium just as the vscode binary is called code.

...without MS branding/telemetry/licensing...

The branding referenced here was the non-freely licensed icons. VSCodium is 99.99% a Microsoft product.

该项目被称为VSCodium，因为调用了原始回购vscode。通过最近的更新，二进制本身codium就像vscode调用二进制一样被调用code。

......没有MS品牌/遥测/许可......

这里引用的品牌是非自由许可的图标。VSCodium是微软产品的99.99％。

检测更新 这个功能不能用对吗？

The codium name is already used by https://www.codium.com.py/en/

Also related #36

I understand @stripedpajamas points and so far the logic makes sense. 👌

Also, the codium name might be unusable unfortunately...

However, I noticed a lot of people in the threads are not happy with the name/branding (1, 2) - is this something there is a community-voting for? Maybe I'll look into a way of changing the name afterwards (via script or similar)...

Also, I just noticed that on macOS VSCode uses simply the name Code everywhere. So this actually differs at the moment... 😱

You raise a good point there. I think it makes sense that the binaries on every platform be called Codium and the repo continue to be called VSCodium, in line with vscode.

@stripedpajamas I think that would make a lot of people very happy 🤗

VSCodium (and a freshly cloned copy of vscode built from source) stores its extension files in ~/.vscode-oss. So if you currently have Visual Studio Code installed, your extensions won't automatically populate. You can reinstall your extensions from the Marketplace in VSCodium, or copy the extensions from ~/.vscode/extensions to ~/.vscode-oss/extensions.

Will the .vscode-oss be renamed? And on Windows the executable file is VSCodium.exe, will it be renamed?

@stripedpajamas, is there any reason to 'customize' VSCodium instead of just replacing non-freely licensed pieces?

In other words, I'd expect VSCodium to be a direct FOSS replacement for VSCode. This means that .vscode is used (ref), binaries are called code (ref), Code is shown on macOS (ref), and it is not possible to have both VSCode and VSCodium installed at the same time (what's the use case for this?).

@1138-4eb

In other words, I'd expect VSCodium to be a direct FOSS replacement for VSCode.

The readme says VSCodium is "freely-licensed binaries with a community-driven default configuration". The 'community-driven default configuration' has so far consisted of:

• a name
• an icon
• disabling telemetry by default
• adding extension marketplace support (which is not present when building from sources as they are in the vscode repo)

Anyone can, of course, run the build scripts in the vscode repo themselves and get "Code - OSS", the FOSS version of Visual Studio Code.

Building the vscode repo results in .vscode-oss as the configuration folder by default (ref). VSCodium doesn't change this so as to share settings/extensions if someone has built from sources manually. Building the vscode repo results in a binary called code-oss (ref). VSCodium changes this to codium. Since VSCodium's default configuration differs from that of a manually built vscode (Code - OSS), I think having a different name reduces confusion.

In regard to having any of Visual Studio Code, Code - OSS, or VSCodium (not to mention the insider versions of all three) installed at the same time -- these pieces of software are all different. Since Visual Studio Code and Code - OSS can be installed alongside each other, I do not see a reason to make VSCodium and any of the others mutually exclusive.

This issue is open to track making the application name in Mac/Windows "Codium" as per this comment.

Would love to have "Codium" in my macOS menu bar. Bonus points for naming the icon "Codium" as well.

@stripedpajamas

The project is called VSCodium because the originating repo is called vscode. With recent updates, the binary itself is called codium just as the vscode binary is called code.

MS repo is called vscode, but MS product (project?) is called Code - OSS.
This repo is called vscodium, so the right project name is Codium (but not Codium - OSS since name Codium already has OSS meaning).

The codium name is already used by https://www.codium.com.py/en/

Also, the codium name might be unusable unfortunately...

Who cares? It is the name of their dev team, their software company is called "Codium S.A." and they have no product called "codium" anyway.
Nobody ever noticed if you didn't place the link. 😄

Also, I just noticed that on macOS VSCode uses simply the name Code everywhere. So this actually differs at the moment... 😱

is there any reason to 'customize' VSCodium instead of just replacing non-freely licensed pieces? In other words, I'd expect VSCodium to be a direct FOSS replacement for VSCode. This means that [...] Code is shown on macOS

I hate how the official version uses the generic name "Code" in the Mac OS X menu bar. There is no reason it can't call itself "Visual Studio Code"; there are applications with longer names, such as "Firefox Developer Edition". The menu bar name actually being unique is one of the reasons I use VSCodium instead of the official version. I suppose "Codium" would still be unique, though.

The more I think of it the more I'm also in favor of making a name change. Codium is much more natural to use.

Also, if someone needs a brand or trademark related motivation, "Visual Studio" is a trademark of Mircosoft.

I too believe that Codium is a much nicer name than VSCodium and since VS has no reason to exists in what that hopes to keep Microsoft branding away. Imagine Microsoft Chrome instead of Edge.

And for what I have understood the name of the editor is actually "Code" if you look at the twitter handle it is "@code" and the name on the macs are "Code", but my theory is that since you can't say "I code in code" it had to have a Microsoft branding before it, like the way apple has to put an "Apple" before the "Watch" or "TV+". And I think since Microsoft already had Visual Studio, pushing a whole new editor that is much better, open source, cross platform and free with the name Microsoft Code could be a real danger to the VS branding, and so why not join forces on that.

@alexdima, @bpasero can I ask you to please tell us the story? I think it's a bit of really really interesting history here

I support renaming without the letters "VS"

This issue has been automatically marked as stale. If this issue is still affecting you, please leave any comment, and we'll keep it open. If you have any new additional information, please include it with your comment!

+1

@daiyam What do you think about adjusting that along with the icon change? "back then" only people that favored this issue and also the PR spoke up. We could showcase that to more users by using the same "news" mechanism.

To anyone coming along "late": a name change has 3 "disruptive" changes:

1. name is different ;) [binary will stay the same for all but Windows were we now have VSCodium.exe
2. you likely need to uninstall the old one when using the new (@paulcarroty likely would add a meta package forwarding vscodium to codium so this would only apply to Windows again)
3. you need to move the settings folder once on your computer, and if using remote workspaces also on each connected computer

@GitMensch Yay, I know, I agree on all your points. It will be a huge mess. Not sure that I want to manage that...
I still do think the rename is a good idea but, in practicality, I don't want to do it due to those issues and the disruptions for everyones.

This should be announced on the welcome page and get released at the beginning of the next year for example.