The current color associated with OCaml on Github is very… bright green. Which doesn’t seem to have much to do with OCaml, and has now reached the point of annoyment for me where I’ve decided it needs to change. These kinds of changes should be anchored in the community though (and also the PR process requires it), so I’d like to ask for your approval, and any objections you might have, before pulling the trigger.
Apparently that color is too close to the color of some other language. As is every other color I’ve tried from the logo and the header of ocaml.org. I’ll have to get back to this after finding something that works.
Is there any summary table for all GitHub languages that will allow to compare?
Kotlin and Haxe seems to be the closest and most troublesome ones. But there’s also BlitzMax, MATLAB, Jupyter, Groovy and Clarion at least in the same space.
It shows just a blank page to me… Seems the wrong CORS request was blocked by the browser:
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://rawgit.com/github/linguist/master/lib/linguist/languages.yml. (Reason: CORS request did not succeed).
That green is unmistakable, it’s from the old ocaml manuals
But that color is super recognizable now! Personally, I like it.
Familiar, not recognizable Personally, even after years, I still associate the color more with shell scripts.
Ah, yeah the manual green is significantly darker, but that probably is it!
Hmm, it works for me in Chromium, Firefox and Epiphany/Gnome Web…
I’ve found a few colors that pass the test, but none of them are particularly appropriate, unfortunately.
Here’s the page with instructions for changing the colour: https://github.com/github/linguist/blob/309acde92e04c86466441afc12992274be938473/CONTRIBUTING.md#changing-the-color-associated-with-a-language
And a test script that checks proximity: https://github.com/github/linguist/blob/309acde92e04c86466441afc12992274be938473/test/test_color_proximity.rb
The only reasonable course of action is to infiltrate the communities of the troublesome languages and propose that they change their color so that the OCaml community can claim that which is rightfully ours! To arms!
Yeah, I’ve been using this. The problem is that the notion of “proximity” is unclear, so it basically boils down to semi-random trial-and-error, and of course running the test is dog slow.
What I’d like is to have all the existing colors plotted in color space, with the proximity tolerance drawn as a circle around each of them. That would make it much easier to see and pick valid colors. Unfortunately since colors are three-dimensional, this isn’t a trivial visualization tool to make. Sounds like a fun project though, if someone has time and is up for the challenge! (pretty please?)
There is a LAB-space color difference with all formulas and visualizations defined. You could check if it’s suitable for you. Something like this R package might be useful:
I like the colour currently being used for ocaml. It’s a memorable colour. I also don’t find it unpleasant. I would vote to keep it as is!
The third is more or less what you get if you ask for “camel” as a fabric color. I don’t think a lot of people would be delighted with the change, but if OCaml is going to be linked with camels (as in the logo), that color does go along with that.
As long as the languages aren’t likely to be used in the same repository having colours close to them seems fine to me
If the logo has been a certain colour for years, that seems like an appropriate choice.
I agree. Unfortunately there’s an actual automatic test that needs to pass, which doesn’t take that into account and which uses a very opaque and complicated measure of proximity. As I understand it, it’s this: http://www2.ece.rochester.edu/~gsharma/ciede2000/ciede2000noteCRNA.pdf
Ugh that’s silly, so there are a finite number of languages that can exist in github’s colour scheme? I wonder if they have a plan for when they run out.