Replies: 2 comments 3 replies
-
|
Good to see someone else with a similar idea. I wish you luck. Related discussion when I tried to change the F# color on GitHub: github-linguist/linguist#6701 And the votes I got by the time: #16563 |
Beta Was this translation helpful? Give feedback.
-
|
Please, let's keep the current purple color for F#. We now have a beautiful shade of purple, possibly the most beautiful color on all of GitHub among all languages supported by linguist. Some languages are stuck with colors that are, to put it mildly, just awful (for example, there's a popular language in a 💩 color). The idea of changing this to the blue from the official F# logo is a huge step backward. That specific shade of blue is unattractive and looks dated. If anything needs to change, perhaps it's time to consider modernizing the F# logo itself? For example in this very purple shade. The argument about VB is completely nonsensical. We shouldn't be making decisions about F# based on a language that is long past its prime. If VB is bothering someone, please change VB's color (I vote for black or transparent) and leave F# alone. |
Beta Was this translation helpful? Give feedback.

Uh oh!
There was an error while loading. Please reload this page.
-
I'm collecting votes to see if the F# community is for changing the GitHub F# color from purple to blue. The colors I'm referring to are the language graphs you see on repositories:

Below is the F# logo.
Here's the current comparison between F# and VB.NET colors, and why it's problematic.

The colors are almost the same, makes it less readable, and the color also doesn't reflect the logo correctly.

From the F# logo, I've picked the lighter blue (#30b9db). It doesn't have to be this one in the end, though.
If this vote gets support, I can forward it to the Linguist team responsible for changing the colors.
I'd love to hear opinions! Vote below 👇
38 votes ·
Beta Was this translation helpful? Give feedback.
All reactions