Meh. It only spans up to (23,59,59) and skips values A-F. As a result it's always a boring shade of blue. Calculating the exact channel values so it spans the entire RGB colorspace isn't very complicated: green = (minutes * 255) / 60; blue = (seconds * 255) / 60;red = (hour * 255) / 24;
Maybe I am being and asshole. I also thought it was cool. One of the things that hubski needs is content, but one thing it needs to be for sure, is original content. That means if you see somethiong cool, you post it here, but if you see something cool in reddit then you post it here, you just become another 9gag. Don't copy titles. I am new from yesterday, so I am no-one to tell you what to post or not, I just wish this place stays as a place for discussion than a place for point earning.
It's okay if it doesn't happen too often. We don't want to become a reddit mirror; if someone wants to repost something for conversational value it's perfectly fine. We don't have strict rules like that here, we just want thoughtful conversation.
I like it, but there should be a slight tweak of the subject line. The author links to a different version, which has a succinct subtitle: "time as a hexadecimal colo(u)r value." I clicked on the link and expected a clock that incremented hexadecimally. Instead the time passes in decimal seconds, minutes, and hours -- but each time segment is parsed as a color address. In other words, "10:35:22" -> red 10, green 35, blue 22. Then the screen changes to that RGB value. I like the strangely calming effect of each new minute pushing the color back to a greener shade. When the 59th second turns over to the zeroeth, all the blue drops out of the background. Then the blue increases and the color feels less alarming. I'll bet the red-realignment at the moment the hour increments is going to be fun! By the way, read the source page.
Sorry, I meant that excitedly. "Oooh, read the source page!" It's simple JavaScript but it's some clean code one could use to teach others.