Skip to content

Revert JavaScript back to its old color#1126

Closed
anaisbetts wants to merge 3 commits intomasterfrom
return-to-sanity
Closed

Revert JavaScript back to its old color#1126
anaisbetts wants to merge 3 commits intomasterfrom
return-to-sanity

Conversation

@anaisbetts anaisbetts changed the title Return to sanity Revert JavaScript back to its old color Apr 25, 2014
@shiftkey
Copy link
Copy Markdown

Seems legit. Anyone wanna second this?

@dannygreg
Copy link
Copy Markdown

👍 do we need to ping anyone in particular? @josh perhaps?

@arfon
Copy link
Copy Markdown
Contributor

arfon commented Apr 25, 2014

I'm 👎 on reverting this. I thought this PR was pretty well thought through. Also, @paulcbetts you've linked to a bunch of tweets, not all of those are negative.

@josh
Copy link
Copy Markdown
Contributor

josh commented Apr 25, 2014

The color change threw me off too, but I'll fully support @mdo's approval.

#979 seems pretty well thought through.

@mdo
Copy link
Copy Markdown

mdo commented Apr 25, 2014

The problem with the color is it's intensity next to other colors. I don't think we need to 100% revert it, but the saturation or vibrancy (? I dunno the specific color terms here) needs to be tuned down.

screen shot 2014-04-25 at 8 36 15 am
screen shot 2014-04-25 at 8 36 39 am
screen shot 2014-04-25 at 8 36 46 am
screen shot 2014-04-25 at 8 37 57 am

Excuse the long number of line breaks now, but I want to visually separate the next set of screenshots for folks.















For example, changing the JS color in those same screenshots to #f1e05a looks like this now:

screen shot 2014-04-25 at 8 38 59 am
screen shot 2014-04-25 at 8 39 06 am
screen shot 2014-04-25 at 8 39 12 am
screen shot 2014-04-25 at 8 39 18 am

@anaisbetts
Copy link
Copy Markdown
Contributor Author

I'm 👎 on reverting this. I thought this PR was pretty well thought through.

I mean, I would agree that it's thought-through, but I would also posit that something must have been incorrect in that thought process because our feedback is primarily (though not exclusively) negative.

Picking the "Official JavaScript Yellow" doesn't match with the rest of the page. There was a specific algorithm for choosing these colors, if you want to make JS yellow, you need to find the nearest matching color from that set.

/cc @github/design

@muan
Copy link
Copy Markdown

muan commented Apr 25, 2014

I'm with @mdo on this. I've been wondering if we made the language bar taller because it's grabbing a lot more attention, then realized it was the color. I'd prefer not reverting, but changing it to @mdo's suggestion.

@mdo
Copy link
Copy Markdown

mdo commented Apr 25, 2014

Alternatively, switch the original JS color to be another language and make the JS one yellow, but setting a precedence for that isn't super helpful.

If the goal at large is to have colors for languages, I say we revert and deal with the (randomly?) chosen original colors.

If the goal at large is to have meaningful or unofficial colors for languages, let's work out a way to apply some color theory to this and pick a JS-y yellow that fits with all our other colors.

I know nothing about the latter, but I'm sure someone else does.

@arfon
Copy link
Copy Markdown
Contributor

arfon commented Apr 25, 2014

There was a specific algorithm for choosing these colors, if you want to make JS yellow, you need to find the nearest matching color from that set.

To be honest I don't feel incredibly strongly either way 😕 . I agree the yellow may be rather too vibrant and this ^^ is a good point @paulcbetts. The last thing I want is for people to find looking at a repo an unpleasant experience.

Given that @maxogden was the author of #979 I feel like we should invite him to defend his PR 😄

Also, @mdo you're suggestion for #f1e05a looks much better to my eyes.

@max-mapper
Copy link
Copy Markdown

If you do a twitter search for 'github yellow' you'll find no overwhelming support either way, people equally love it or dislike it.

Most of the negative feedback seems to be from people with (perhaps) really high brightness monitors who complain that the yellow is too jarring. I'm +1 on changing to #f1e05a for this reason.

@anaisbetts
Copy link
Copy Markdown
Contributor Author

I'm okay with the darker version, lemme reset this PR and rig it to use #f1e05a instead

@arfon
Copy link
Copy Markdown
Contributor

arfon commented Apr 27, 2014

Fixed in #1135

@arfon arfon closed this Apr 27, 2014
@anaisbetts anaisbetts deleted the return-to-sanity branch May 4, 2014 02:43
@github-linguist github-linguist locked as resolved and limited conversation to collaborators Jun 18, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

8 participants