mirror of
https://github.com/VSCodium/vscodium.git
synced 2026-04-09 14:14:16 -05:00
[Discussion] Rename VSCodium to Codium #1409
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @jannik-mohemian on GitHub.
I hope this is the right format to do this
Rename to
CodiumWhy not remove the
VS(akaVisual Studio) from the name as well.In essence VSCodium is
binary releases of VS Code without MS branding/telemetry/licensing(quote from GitHub repository description)In this case we can remove the
VS, which is a very big MS brand, as well...What do you think?
@jannik-mohemian commented on GitHub:
Also related #36
@paulcarroty commented on GitHub:
The
codiumname is already used by https://www.codium.com.py/en/@hexpunk commented on GitHub:
See also #28
@git10135405 commented on GitHub:
检测更新 这个功能不能用对吗？
@stripedpajamas commented on GitHub:
The project is called VSCodium because the originating repo is called
vscode. With recent updates, the binary itself is calledcodiumjust as thevscodebinary is calledcode.The branding referenced here was the non-freely licensed icons. VSCodium is 99.99% a Microsoft product.
@linsui commented on GitHub:
Will the
.vscode-ossbe renamed? And on Windows the executable file is VSCodium.exe, will it be renamed?@jannik-mohemian commented on GitHub:
I understand @stripedpajamas points and so far the logic makes sense. 👌
Also, the
codiumname 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)...
@jannik-mohemian commented on GitHub:
@stripedpajamas I think that would make a lot of people very happy 🤗
@stripedpajamas commented on GitHub:
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.
@jannik-mohemian commented on GitHub:
Also, I just noticed that on macOS VSCode uses simply the name
Codeeverywhere. So this actually differs at the moment... 😱@eine commented on GitHub:
@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
.vscodeis used (ref), binaries are calledcode(ref),Codeis 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?).@pixelclef commented on GitHub:
Would love to have "Codium" in my macOS menu bar. Bonus points for naming the icon "Codium" as well.
@stripedpajamas commented on GitHub:
@1138-4EB
The readme says VSCodium is "freely-licensed binaries with a community-driven default configuration". The 'community-driven default configuration' has so far consisted of:
vscoderepo)Anyone can, of course, run the build scripts in the
vscoderepo themselves and get "Code - OSS", the FOSS version of Visual Studio Code.Building the
vscoderepo results in.vscode-ossas 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 thevscoderepo results in a binary calledcode-oss(ref). VSCodium changes this tocodium. Since VSCodium's default configuration differs from that of a manually builtvscode(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.
@crabvk commented on GitHub:
@stripedpajamas
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).
@crabvk commented on GitHub:
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. 😄
@bittner commented on GitHub:
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.
@github-actions[bot] commented on GitHub:
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!
@sakunix commented on GitHub:
I support renaming without the letters "VS"
@pouyakary commented on GitHub:
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
@jobukkit commented on GitHub:
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.
@GitMensch commented on GitHub:
@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:
@evur commented on GitHub:
This should be announced on the welcome page and get released at the beginning of the next year for example.
@daiyam commented on GitHub:
@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.
@daiyam commented on GitHub:
+1