Live data from Hacker News

#c0ffee is the color

c0ffee.surge.sh

81–90 of 127 posts

Re: #c0ffee is the color

#81
post #44

Earlier quoted context omitted.

I also plan to use 54FE57 somewhere. Have to do that. Though with the numbers in the beginning it's not as readable as e.g. BADA55.

Hmm. BADA55 didn't make it on to that site, strangely enough.

They parsed an English dictionary. You mean the dictionary didn't contain badass? gasp :)

Re: #c0ffee is the color

#82
The idea is nice, but (as a suggestion) I would add a drop down to "strict" where you can tick whether to include 0 (zero) and 1 (one) as respectively O and I, which is what everyone would likely read as well as - maybe - 5=S while the 1 as L (as in 1337) and the 7=T are far less intuitive. To give anyone freedom of choice maybe adding a "selectively strict" button with ticks for each leet letter would be ideal (as an example I cannot read the 2 as R as it is used on http://bada55.io/ ).

Re: #c0ffee is the color

#83

Earlier quoted context omitted.

Yes but you grew up typing hex codes into a home computer connected to a tape drive. You know what 8192 looks like in binary but everything beyond 65535 you struggle with because you didn't have the registers for that on your 6502A. It probably irritates you to see images scaled to 1000 pixels rather than 1024. What about that jpeg cell that is not 8 pixels square? Think of the computational overhead and the need to…

> I think is important but it seems most front end developers would prefer not to know. This is my experience. There are two types of people in this industry, people who want to make money quick and those who are technologists.

What would you guess is the ratio of each?

Re: #c0ffee is the color

#84

Earlier quoted context omitted.

Yes but you grew up typing hex codes into a home computer connected to a tape drive. You know what 8192 looks like in binary but everything beyond 65535 you struggle with because you didn't have the registers for that on your 6502A. It probably irritates you to see images scaled to 1000 pixels rather than 1024. What about that jpeg cell that is not 8 pixels square? Think of the computational overhead and the need to…

> I think is important but it seems most front end developers would prefer not to know. This is my experience. There are two types of people in this industry, people who want to make money quick and those who are technologists.

I disagree. Not wanting to learn hex does not make you less of a techie. One can only focus on so much, and tech is huge.

Re: #c0ffee is the color

#85
post #83

Earlier quoted context omitted.

> I think is important but it seems most front end developers would prefer not to know. This is my experience. There are two types of people in this industry, people who want to make money quick and those who are technologists.

What would you guess is the ratio of each?

In my experience, I tend to think it's something like 30% technologists, 70% money makers. Unfortunately, barely anyone (including myself) wants to see themselves as the second group (for the record, I think I'm on the second group).

Re: #c0ffee is the color

#88
post #21

Earlier quoted context omitted.

These CSS colors consist of 3 bytes in hex, the first gives the red value, second green and the last is blue. So: #FF0000 = 0xFF, 0x00, 0x00, which is pure red #0000FF = 0x00, 0x00, 0xFF, which is pure blue #FF00FF = 0xFF, 0x00, 0xFF, which is red and blue mixed, so it's purple (violet) #FFFFFF = 0xFF, 0xFF, 0xFF, all colors combined is white etc #C0FFEE = 0xC0, 0xFF, 0xEE, so by 'parsing' it in your head yo can see…

Yes but you grew up typing hex codes into a home computer connected to a tape drive. You know what 8192 looks like in binary but everything beyond 65535 you struggle with because you didn't have the registers for that on your 6502A. It probably irritates you to see images scaled to 1000 pixels rather than 1024. What about that jpeg cell that is not 8 pixels square? Think of the computational overhead and the need to…

You don't even have to decode the actual number, just comparatively figure out which one 'looks bigger'. In more steps than necessary to be abundantly explicit:

Step 1: group into two characters each.

Step 2: know that hex is an extension of decimal that adds the digits A-F after 9. So just like 0Step 3: find the biggest and smallest groups by comparing the first digits of each. If they match they're pretty close.

Step 3a (optional): guestimate the intensity of each color by thinking of the first digit on the scale from 0 is least intense to F is most intense. (5: somewhat less than half, D: pretty close to max, 1: almost none etc)

Step 4: use your knowledge of additive color mixing to guestimate the color.

You don't need to be able to map each digit to its' decimal equivalent first to get a general guess. If you're missing Step 4, then you can still figure out mostly-primary colors like #D53A1F. Step 1 should be trivial. Step 3 can be guestimated.

Re: #c0ffee is the color

#89

I'm surprised no one yet has mentionned the famous stack overflow question: https://stackoverflow.com/questions/8318911/why-does-html-th... . TLDR; For legacy reasons, some words produce valid colors even if they don't respect the standard color formats. For example, "chucknorris" produces red.

Someone should make a list of all words and common phrases that result in a color different from #000000 and then go through them all and pick out the interesting ones.

By the way I didn't see any mention of max length. Is there a limitiation to the length of the color string?

Bonus question: What color would the complete works of Shakespeare be? Take all of his scene play manuscripts found on Project Gutenberg but excluding duplicates if any, sort them in the order they were originally published and concatenate into a single string.

Post reply on HN