OK Go Goes HTML5 171
edumacator writes "The YouTube sensation OK Go has just released their latest video using HTML5. The video is pretty cool itself, but the interactive feature is great." It looks like the interactive stuff only works in Chrome.
Youtube Sensation??? (Score:5, Insightful)
WT Heck. This video is so annoying I couldn't even finish watching it. And a web site that says "You have to download and install a Google product to use me"? Um, no thanks?
It takes me about 3 seconds to leave a web site that says I have to download a Google product to view it.
Re:This site works best with... (Score:5, Insightful)
"We recommend"? No. We DEMAND . If you mean it, say it. Or provide a "try it anyway" button.
Re:IRONY OVERLOAD (Score:5, Insightful)
Chrome Advertisement, people. Nothing more.
Google is evil. RMS was right. (Score:5, Insightful)
Google. You're turning evil. In fact, over the last year you've turned way more evil than I could ever have anticipated. What with Chromebooks turning Chrome into a 'proprietary apps' platform, when those apps, save for their 'Chrome packaging' should have been normal webapps for any browser ... and now this.
I'm out.
Note:. This didn't even work in Chromium. CHROMIUM!!! I had to get 'Google Chrome' for it to work.
Don't you hate it when that blasted RMS eventually keeps turning out right all the time ... :(
Bottom left side of the page (Score:5, Insightful)
"This is a Chrome Experiment"
and this is me closing the page *click*
Re:This site works best with... (Score:4, Insightful)
> and Chrome really uses open standards and
> protocols.
Except it doesn't. It uses a mishmash of open standards, proposed open standards, things they wrote up and threw over the "standards" wall, and flat-out proprietary extensions.
Seriously, try to implement CSS Animations based on the "draft spec". You can't. It's too vague to actually implement it without reverse-engineering WebKit first. And that's one of the ones that people are actually planning to standardize, unlike some of the other stuff Chrome is implementing.
> The problem is that Google is developing it at such
> an astonishing pace
The "problem" is that Google is implementing random things, exposing them to the web, encouraging people to use them, and maybe writing up a vague description of what the functionality is supposed to do (not enough to actually implement interoperably) and calling that a "standards draft".
Pretty similar to the way Microsoft did OOXML, actually. Except they wrote a better spec.
Hmph. (Score:3, Insightful)
Okay, so the message when visiting with Safari says "We're sorry, but this content was designed with the browser Google Chrome in mind. As a result, it may not work properly in your current browser. We recommend using Google Chrome." So I think, "Well, Chrome essentially cribbed their HTML5 engine from Safari, so I should be good. I'll give it a try." Unfortunately, there's no way to get past the message. Perhaps they should rephrase "It may not work in your current browser" to "We won't let you view this with anything but Chrome." Ah well. It will take more than an interactive movie video to make me install Chrome. *close*