-
Notifications
You must be signed in to change notification settings - Fork 4.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
List of languages pending colour correction or addition #4506
Comments
I would like to add:
|
Added, thank you! |
|
I'd recommend for Eiffel: The current color for the Eiffel programming language is The current color of Ada ( |
@david-tamar Regarding the unknown colour sources: it's quite likely they were selected at random, possibly because the official colour was unknown or unavailable. Added Eiffel to the OP. |
@lildude Any update? |
Nope. Still waiting on GitHub Design to give me the 👍 or 👎 on my request to drop the proximity enforcement. |
Hopefully they can prioritise this or something, because there's a lot of stuff blocked on this... 😞 |
I'd like to thumbs-up your issue, can you give me a link? |
I think it's internal. As in, visible only to GitHub staff. If it were public, I'm sure we'd be seeing links to this issue being referenced in this thread's activity feed. E.g., stuff like "@lildude referenced this issue on 19 Sep" and what-have-you. |
I'd like to add Prisma to the list 🙏
Thanks! |
Hey @Weakky, 👋 I'll add it once you've actioned #4668 (comment). 😉 EDIT: I've updated the list. Thanks for the quick response! 👍 |
Wikipedia cites that the US Department of Defense (which sponsored Ada in the first place) awarded an exclusive contract to NYU to implement a free implementation of Ada strictly under FSF's GPL. NYU's Ada Translator (widely abbreviated today as GNAT, where the G stands for GNU, by association with FSF's GNU GPL) is in fact the only standard free implementation of Ada that is both officially sponsored by the US government, and freely available for everyone. It's therefore most likely that every Ada project on GitHub uses NYU's implementation, since it's officially distributed on most Linux distributions like Debian, Fedora, Ubuntu and Red Hat. It's also the go-to implementation for Windows and Mac users. AdaCore, a major contributor of NYU's Ada, is also targeting enterprise and corporate clients with a full featured infrastructure and IDE that ship with NYU's GNAT as the default implementation. I searched the internet for historical logos or mascots of Ada, but I did not find any official logos or mascots that featured any other colors than plain black on white, and dark blue, and yet most of those commercial graphics (either from AdaCore or communities) came way after NYU's work on Ada. |
@david-tamar This is worth being filed as a new issue, especially because there are guidelines in place for changing the colours of well-known languages. This issue is only for colours that are unambiguously correct/official, but are blocked from use entirely due to another colour being slightly too similar. |
@Alhadis, It turns out the current color is actually not arbitrary as I thought. A user on Reddit's Ada community has shown me the connection between Ada and the green color. Ada was actually code-named “Green” by its original author in its very early stage at least 12 years before New York University worked on the Ada Translator, so never mind.
|
A bit later after it's approval but I'd like to add:
It is currently: Thanks :) |
Hey @gen-angry, sorry for the slow response. 👋 I've added it to the list, thanks! |
Could you also add:
It's currently grouped under HTML. |
@ObserverOfTime If it's grouped under HTML, the colour won't be visible anyway (because such "child" languages always inherit their parent's colour, irrespective of |
I am aware but I think it should be ungrouped. It's similar to Vue which isn't part of the HTML group. Should I have mentioned it in #4291? |
Yes, actually. 👍 |
From #4969
I'm thiiiiiiis close to doing it and dealing with the fallout if and when it happens 😬. If I were to 🔥 it, do we want to allow duplicate colours? I'm thinking not at first as we'll end up with a million identical reds or blues. |
I'll copy+paste my earlier response so folks here will see it:
|
🤦 Of course. I didn't think about that. |
On second thought, let's just get it over with. #4291 will take all of 10 minutes to address, and the changes will be noticed—and warmly-welcomed—by virtually every web developer on GitHub. Since we're on the verge of a new release, I say: LET'S DO THIS SHIT. |
* Abolish restrictions governing colour choices * Add/fix incorrect or missing language colours Resolves: #4506 Co-authored-by: Colin Seymour <colin@github.com>
* Abolish restrictions governing colour choices * Add/fix incorrect or missing language colours Resolves: github-linguist#4506 Co-authored-by: Colin Seymour <colin@github.com>
#4417 was closed yesterday, so I felt it might be beneficial to keep a record of languages whose colours are incorrect (according to their branding or community's "preferred" colour). That way they won't fade into obscurity after being blocked for so long.
Now, these fixes are blocked because of an ugly tangle of colour-proximity violations, which was previously discussed in
#4291
. Since it's unclear when (or even if) a decision will be made on GitHub's part, I'm compiling them here so nobody forgets. 👍 The list is incomplete and I've probably missed a lot, so feel free to make amendments as you see fit.#ff0000
(source: logo)#1797c0
(source:#4417
)#f7523f
#244776
(source: "inherited" from CoffeeScript)#4d6977
(source: logo)#ff0000
(source: logo)#ece2a9
#f7931e
#f2a542
#1d365d
#42bff2
#083fa1
(source: original colour value)#3D57C3
(source: "m" in logo)#da291c
(source:#3141
)#0C344B
#a86454
#c6538c
#a53b70
#2b2b2b
#f69e1d
(source: logo)#ff6347
#ff9900
(source: logo)#c1d026
#4f87c4
(source: logo)#2c3e50
(source:#4448
)#cb171e
(source: logo)Sidenotes
Some of these are
data
orprose
languages, which normally don't displaycolours, but some are of relevance now that the
linguist-detectable
attributecan reveal them in a project's statistics-bar. I'm being conservative and only
adding colours for data formats (like SVG or YAML) that have an obvious colour
defined by their logos.
Many of these are markup languages waiting to be degrouped. Degrouping them now
with missing/incorrect colours would be disruptive to many users.
I'm reluctant to tweak the colours of "well-known/famous" languages like JavaScript
or TypeScript, which have the highest degree of visibility on GitHub. Even if they
currently deviate only a few shades from their official colours, I predict astute
users with oddly-calibrated monitors will notice the shift immediately.
The text was updated successfully, but these errors were encountered: