# Name suggestions for VS Code

**URL:** https://discourse.julialang.org/t/name-suggestions-for-vs-code/43958
**Category:** VS Code
**Created:** [July 30, 2020, 9:59am UTC](https://discourse.julialang.org/t/name-suggestions-for-vs-code/43958 "2020-07-30T09:59:30Z")
**Posts on this page:** 20
**Page:** 3

<div class="post-metadata">

### Author: ![heliosdrm](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/heliosdrm/32/3851_2.png) [@heliosdrm](https://discourse.julialang.org/u/heliosdrm)
#### Post date: [July 31, 2020, 1:43pm UTC](https://discourse.julialang.org/t/name-suggestions-for-vs-code/43958/43 "2020-07-31T13:43:03Z")

</div>

> [@helgee](#):
>
> I can imagine that we lost quite a few people at the start of their journey because of the confusing facts that JuliaPro cannot do what regular Julia can and that the _pros_ aren’t using the former.

This depends on how you interpret what “Pro” refers to: I always thought on people working in _pro_fessional environments, where IT people prefer packaged solutions with “batteries included” and possible support - which paid plans of JuliaPro provide indeed.

---

<div class="post-metadata">

### Author: ![helgee](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/helgee/32/2022_2.png) [@helgee](https://discourse.julialang.org/u/helgee)
#### Post date: [July 31, 2020, 2:05pm UTC](https://discourse.julialang.org/t/name-suggestions-for-vs-code/43958/44 "2020-07-31T14:05:49Z")

</div>

That is surely the correct interpretation of the name.

At the same time there are lots of (consumer) products where a “Pro” suffix just indicates that this is a slightly shinier, more expensive version of another product (see Airpods Pro, Windows 10 Pro). Thus, beginners seem to expect to get a more featureful Julia when they download JuliaPro instead of the more constrained environment that it actually aims to be. Calling it something like “JuliaEnterprise” might avoid this ambiguity…

If you search for “JuliaPro” on this forum, you will find tons of beginners getting stumped.

---

<div class="post-metadata">

### Author: ![NiclasMattsson](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/niclasmattsson/32/21988_2.png) [@NiclasMattsson](https://discourse.julialang.org/u/NiclasMattsson)
#### Post date: [July 31, 2020, 2:37pm UTC](https://discourse.julialang.org/t/name-suggestions-for-vs-code/43958/45 "2020-07-31T14:37:31Z")

</div>

On balance I am also in the “no name” camp - but if the team decides they want a dedicated name then I suggest **Jove**.

Rationale: [in this slide of his excellent Juliacon presentation](https://www.youtube.com/watch?v=rQ7D1lXt3GM&t=4m04s), Sebastian put forth three criteria for a new name:

- starts with J
- relation to Juno and/or Jupiter
- short and recognizable

In Roman mythology, Jove is a synonym for Jupiter, the capo-di-tutti-capi of gods. (Actually if I recall correctly Jupiter is a contraction of Jove-Pater or Father Jove in Latin.) His wife is Juno.

“Jove” is short and recognizable, sounds kind of similar to Code and for those who need everything to be an acronym, it could mean “ **J** ulia **V** S Code **E** ditor” - no idea what the O stands for though. 😄

---

<div class="post-metadata">

### Author: ![CameronBieganek](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/cameronbieganek/32/6915_2.png) [@CameronBieganek](https://discourse.julialang.org/u/CameronBieganek)
#### Post date: [July 31, 2020, 3:28pm UTC](https://discourse.julialang.org/t/name-suggestions-for-vs-code/43958/46 "2020-07-31T15:28:51Z")

</div>

I’m in favor of leaving the name the way it is.

If I had to pick a new name, I would go with the repurposed Julia Studio.

---

<div class="post-metadata">

### Author: ![jlperla](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/jlperla/32/34332_2.png) [@jlperla](https://discourse.julialang.org/u/jlperla)
#### Post date: [July 31, 2020, 4:51pm UTC](https://discourse.julialang.org/t/name-suggestions-for-vs-code/43958/47 "2020-07-31T16:51:08Z")

</div>

Along these lines, perhaps following whatever naming/branding standards exist for the ecosystem.

For vscode, go to [All categories Extensions - Visual Studio Marketplace](https://marketplace.visualstudio.com/search?target=VSCode&category=All%20categories&sortBy=Installs) and search for different languages. I find that there is “branding” on almost none of the primary language extensions. Rust, python, dart, C#, ruby, etc. are all just that. e.g. [https://github.com/rust-lang/vscode-rust](https://github.com/rust-lang/vscode-rust) etc.

You can find exceptions, but it is pretty clear what the standard is for the “primary” extension in vscode. I suspect that if there was branding involved, no matter what it was, that people would confusingly think that it is not the standard “julia extension” or perhaps something a commercial vendor is selling.

Also, I lost track of the number of times people thought Juno and Atom extensions were different ways to access julia due to the branding.

---

<div class="post-metadata">

### Author: ![davidanthoff](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/davidanthoff/32/223493_2.png) [@davidanthoff](https://discourse.julialang.org/u/davidanthoff)
#### Post date: [July 31, 2020, 6:29pm UTC](https://discourse.julialang.org/t/name-suggestions-for-vs-code/43958/48 "2020-07-31T18:29:42Z")

</div>

> [@oheil](#):
>
> So it must be **JUPP**

YES! That is cleary my favorite option, if it was just me I would rename this instant!

---

<div class="post-metadata">

### Author: ![davidanthoff](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/davidanthoff/32/223493_2.png) [@davidanthoff](https://discourse.julialang.org/u/davidanthoff)
#### Post date: [July 31, 2020, 6:31pm UTC](https://discourse.julialang.org/t/name-suggestions-for-vs-code/43958/49 "2020-07-31T18:31:25Z")

</div>

Also, I’m hearing the “we don’t need a name” fraction loud and clear. I’m personally quite sympathetic to that view, but lets keep the ideas coming and then we (the team) will sit down when things have quieted down a bit and figure this out 🙂

---

<div class="post-metadata">

### Author: ![tbeason](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/tbeason/32/15898_2.png) [@tbeason](https://discourse.julialang.org/u/tbeason)
#### Post date: [July 31, 2020, 6:35pm UTC](https://discourse.julialang.org/t/name-suggestions-for-vs-code/43958/50 "2020-07-31T18:35:38Z")

</div>

Plus one for Team Boring.

---

<div class="post-metadata">

### Author: ![bernhard](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/bernhard/32/2619_2.png) [@bernhard](https://discourse.julialang.org/u/bernhard)
#### Post date: [July 31, 2020, 7:10pm UTC](https://discourse.julialang.org/t/name-suggestions-for-vs-code/43958/51 "2020-07-31T19:10:20Z")

</div>

Same here.  
It seems natural (for new users?) to google julia vscode. Keep it simple?

---

<div class="post-metadata">

### Author: ![string-dot-byte](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/string-dot-byte/32/17741_2.png) [@string-dot-byte](https://discourse.julialang.org/u/string-dot-byte)
#### Post date: [July 31, 2020, 7:26pm UTC](https://discourse.julialang.org/t/name-suggestions-for-vs-code/43958/52 "2020-07-31T19:26:45Z")

</div>

Yeah, I can relate. I’m new to Julia and if I were to look for a plugin I would directly search up “Julia” or something of that sort. As for me searching in other programming languages would be the same mind reference to search up the programming language name itself and just scroll until I find an interesting one or one that I am in need of.

I wouldn’t think of any other things that would come necessary to me in regards of the name.

---

<div class="post-metadata">

### Author: ![aaraujo71](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/aaraujo71/32/10635_2.png) [@aaraujo71](https://discourse.julialang.org/u/aaraujo71)
#### Post date: [August 1, 2020, 1:53am UTC](https://discourse.julialang.org/t/name-suggestions-for-vs-code/43958/53 "2020-08-01T01:53:58Z")

</div>

VS Julia

---

<div class="post-metadata">

### Author: ![EarthGoddessDude](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/earthgoddessdude/32/13003_2.png) [@EarthGoddessDude](https://discourse.julialang.org/u/EarthGoddessDude)
#### Post date: [August 1, 2020, 2:32am UTC](https://discourse.julialang.org/t/name-suggestions-for-vs-code/43958/54 "2020-08-01T02:32:33Z")

</div>

Team Non-Boring vote for **Demeter**. I am may be biased…

Also **Prometheus** , for he giveth fire and knowledge to mere mortals.

---

<div class="post-metadata">

### Author: ![ettersi](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/ettersi/32/6829_2.png) [@ettersi](https://discourse.julialang.org/u/ettersi)
#### Post date: [August 1, 2020, 3:38am UTC](https://discourse.julialang.org/t/name-suggestions-for-vs-code/43958/55 "2020-08-01T03:38:55Z")

</div>

Quoting [EricForgy](https://discourse.julialang.org/t/name-suggestions-for-vs-code/43958/25) quoting David (Anthoff, I assume):

> We will not change the name of the extension itself in the marketplace, we would probably change the name of the publisher and call the overall effort this new name. We would also use that name in things like discourse forum etc. But the extension in the marketplace itself would still just be called Julia.

So as far as I understand, the Julia VS Code plugin will always appear as “Julia” from within VS Code. The name discussed here would be used for things like the [website](https://www.julia-vscode.org/), the [GitHub organisation](https://github.com/julia-vscode), and generally in statements like “I did this in [Julia plugin for VS Code], and then that happened”.

The last example demonstrates what I meant by [“clumsy”](https://discourse.julialang.org/t/name-suggestions-for-vs-code/43958/32). For statements like this one, you want a short, standardised name like “VS Code Julia” or “Julia Code” or any branded name like “Juno”, “Jules”, etc., so there’s no [decision fatigue](https://www.businessinsider.com/successful-people-like-barack-obama-wear-the-same-thing-every-day-2018-2?fbclid=IwAR1MduWZ0vCi4CqBY48Tq70oqI9qYrOBKz9vR9DCsVf4J9EyQ7T2ef9D9OI) for the author and easier parsing for the readers.

---

<div class="post-metadata">

### Author: ![sylvaticus](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/sylvaticus/32/203883_2.png) [@sylvaticus](https://discourse.julialang.org/u/sylvaticus)
#### Post date: [August 1, 2020, 7:42am UTC](https://discourse.julialang.org/t/name-suggestions-for-vs-code/43958/56 "2020-08-01T07:42:31Z")

</div>

My ordered set of preferences (subject to agreement with name owners, if any):

- Juno
- Julia Code
- Julia Studio

Not neede to be a marketing guy to forecast that the first option in particular would faster user migration to the new IDE.

---

<div class="post-metadata">

### Author: ![lostella](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/lostella/32/356_2.png) [@lostella](https://discourse.julialang.org/u/lostella)
#### Post date: [August 1, 2020, 8:24am UTC](https://discourse.julialang.org/t/name-suggestions-for-vs-code/43958/57 "2020-08-01T08:24:13Z")

</div>

> [@davidanthoff](#):
>
> I am a Bayern Munich member, so anything remotely related to Juve is not an option, I’m afraid 🙂

Fiorentina supporter here, and I couldn’t agree more

---

<div class="post-metadata">

### Author: ![BLI](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/bli/32/37206_2.png) [@BLI](https://discourse.julialang.org/u/BLI)
#### Post date: [August 1, 2020, 10:44am UTC](https://discourse.julialang.org/t/name-suggestions-for-vs-code/43958/59 "2020-08-01T10:44:34Z")

</div>

I don’t have strong feelings about the name. I would guess that “Juno” would be somewhat confusing, so maybe “Juno 2.0” or “Juno Studio” – or “Juno Code”. “Code” has the advantage of having a single syllable (and perhaps also connect to Codespaces). However, “Studio” will perhaps better cover plans of extensions such as a “Julia notebook”. And “Julia Studio” is probably also ok.

---

<div class="post-metadata">

### Author: ![Tim\_G](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/tim_g/32/11039_2.png) [@Tim\_G](https://discourse.julialang.org/u/Tim_G)
#### Post date: [August 1, 2020, 11:04am UTC](https://discourse.julialang.org/t/name-suggestions-for-vs-code/43958/60 "2020-08-01T11:04:12Z")

</div>

This crossed my mind:

**Julio** : A Julia plugin for Visual Studio

But how to pronounce “Julio”?

---

<div class="post-metadata">

### Author: ![anon92994695](https://avatars.discourse-cdn.com/v4/letter/a/ce7236/32.png) [@anon92994695](https://discourse.julialang.org/u/anon92994695)
#### Post date: [August 1, 2020, 12:05pm UTC](https://discourse.julialang.org/t/name-suggestions-for-vs-code/43958/61 "2020-08-01T12:05:47Z")

</div>

Why not just “JuliaCode”?  
Fits inline with JuliaRun, JuliaTeam, etc. Also Code is slang for VSCode I think. But it follows the naming conventions for Julia packages.

---

<div class="post-metadata">

### Author: ![aaraujo71](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/aaraujo71/32/10635_2.png) [@aaraujo71](https://discourse.julialang.org/u/aaraujo71)
#### Post date: [August 1, 2020, 1:59pm UTC](https://discourse.julialang.org/t/name-suggestions-for-vs-code/43958/62 "2020-08-01T13:59:19Z")

</div>

Julia.VS  
Julia VS  
VS Julia

---

<div class="post-metadata">

### Author: ![CameronBieganek](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/cameronbieganek/32/6915_2.png) [@CameronBieganek](https://discourse.julialang.org/u/CameronBieganek)
#### Post date: [August 1, 2020, 7:26pm UTC](https://discourse.julialang.org/t/name-suggestions-for-vs-code/43958/63 "2020-08-01T19:26:54Z")

</div>

The problem with JuliaCode is the similarity to “Julia code”. Then if I said out loud “I’m writing Julia code”, it would be ambiguous.

[Previous page](https://discourse.julialang.org/t/name-suggestions-for-vs-code/43958.md?page=2)

[Next page](https://discourse.julialang.org/t/name-suggestions-for-vs-code/43958.md?page=4)
