Slashdot Mirror


OK Go Goes HTML5

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.

25 of 171 comments (clear)

  1. IRONY OVERLOAD by suso · · Score: 5, Funny
    • 1. OK Go - Probably brought initial wave of people to Youtube
    • 2. New video promotion trying to show support for HTML5, an open standard and helps bring an end to flash.
    • 3. Website message when visiting with Firefox 5: We're sorry, but this content was designed with the browser Google Chrome in mind.
    • 4. Google trying to not be evil, yet icons at the bottom saying "Made with some friends from Google"

    WTF? I think I'm going to throw up now.

    1. Re:IRONY OVERLOAD by Anonymous Coward · · Score: 5, Insightful

      Chrome Advertisement, people. Nothing more.

  2. Re:This is the gayest shit I've ever seen. by Flyerman · · Score: 3, Funny

    You sir, owe it to yourself to observe more frequently the fecal matter of homosexuals. It will spare you the embarrassment of making such an incorrect statement again.

  3. This site works best with... by QuasiSteve · · Score: 3

    "This site works best with..." remember the loathe 'we' used to have for that phrase, because it was almost invariably followed by "Internet Explorer"?

    Welcome to semi-recent developments where that phrase makes its comeback, now to be followed by Google Chrome.

    So I'll augment my post from yesterday with:
    How about installing Google Chrome when you want to watch an online presentation purportedly made using HTML5 standard tech?

    1. Re:This site works best with... by v1 · · Score: 4, Insightful

      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

      "We recommend"? No. We DEMAND . If you mean it, say it. Or provide a "try it anyway" button.

      --
      I work for the Department of Redundancy Department.
    2. Re:This site works best with... by QuasiSteve · · Score: 2

      I think the difference is not as big as some may think it to be, though.

      Ultimately if a site developer chooses to use certain desired (by them) features that make the site work better in a particular browser and slaps on a "site works best in..." disclaimer, then it's still that site developer's doing.

      Whether those features are proprietary (not counting ActiveX bits, which were rarely the reason for such disclaimers) or part of a work-in-progress standard (HTML5 has not been finalized) doesn't really matter much there.

      This in no way undermines what you're saying about development pace, mind. But when you couple it with the fact that Google helped make the page, you have to ask yourself if they really are just trying to be 'hip with Web 2.0' and making an interactive HTML5 video, or whether they're really just helping push Google Chrome onto more desktops by virtue of using HTML5 features that they undoubtedly knew would only work proper in Google Chrome / Chromium.

    3. Re:This site works best with... by bonch · · Score: 2, Informative

      So it's more closed-open bullshit from Google?

      If Chrome uses open standards and protocols, there's no reason for it to be Chrome-only. You say competitors are "left in the dust" because Chrome is developed at such an "astonishing pace" (it's easy to appear that way when you constantly bump major version numbers), but Chrome is based on the open source WebKit, the same engine Safari uses that was developed mostly by Apple. There's nothing particularly unique to Chrome except for its Javascript engine, which doesn't use some futuristic version of Javascript that nobody else can run.

      Not to mention that the claim that Chrome is based entirely on "open standards and protocols" is ridiculous--the browser ships the closed-source, proprietary Flash plug-in and supports both AAC and MP3 audio playback.

    4. Re:This site works best with... by BZ · · Score: 3, 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.

    5. Re:This site works best with... by BZ · · Score: 2

      And to be clear, the real problems are encouraging people to use the new stuff and pretending it's open standards when it's not and when it's not ready for production use. And then people doing just that, whether because they don't know any better or because they don't care, on public-facing sites.

    6. Re:This site works best with... by Lennie · · Score: 3, Informative

      http://caniuse.com/

      It depends, if you look at the numbers:

      "Calculation of support for currently selected criteria" (Recommendation, Proposed Rec., Candidate Rec., Working Draft, Other):

      Current:
      IE9: 58%
      Firefox 5: 84%
      Safari 5.1: 82%
      Chrome 12: 89%
      Opera 11.5: 76%

      Near Future:
      IE9: 58%
      Firefox 6: 87%
      Safari 5.1: 82%
      Chrome 13: 89%
      Opera 12.0: 79%

      Farther future:
      IE 10: 71%
      Firefox 7: 87%
      Safari 6: 82%
      Chrome 14: 88%
      Opera 12.1: 79%

      --
      New things are always on the horizon
    7. Re:This site works best with... by BZ · · Score: 2

      Almost everything in that list is pie-in-the-sky stuff of various sorts (in-progress specs, etc).

      The IE10 numbers are based on the released IE10 preview builds.

      The Firefox numbers are "stagnating" from Firefox 5 (released June 2011) to Firefox 7 (planned to be released Sept 2011). A few percentage points every three months is not that bad. ;)

    8. Re:This site works best with... by BZ · · Score: 2

      > As long as the standards are open

      Define "open"? Do you mean "we wrote up something based on our implementation, sorta, and published it", or do you mean "a bunch of people got together and figured out how this should work across a variety of use cases"?

      The two cases are very different, and both have catastrophic failure modes as well as some amazing success modes.

    9. Re:This site works best with... by BZ · · Score: 2

      NPAPI Flash (the kind that Chrome uses) is not commonly preinstalled on computers, though some OEMs do preinstall it. The commonly preinstalled thing is ActiveX Flash (the kind IE uses).

      So yes, Chrome is helping spread Flash. And vice versa: the Flash installer (e.g. if you're using Firefox or Opera) bundles Chrome onto your computer if you're not careful

  4. Youtube Sensation??? by Anonymous Coward · · 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.

  5. Re:sorry, shitty band. by QuasiSteve · · Score: 3

    sorry, shitty band.

    Opinions - you're entitled to have 'm.

    and even if it were great, wtf. since when did slashdot become an art channel for specific releases

    Since the release involved HTML5, something that jives well within the 'nerd' demographic? (as does the band, to an extent, given that they're not generally 'pop' and make wacky videos).
    Slashdot did the same with Radiohead's open sourcing of their music video:
    http://tech.slashdot.org/story/08/07/18/1436211/Radiohead-Open-Sources-Music-Video
    Be glad that this time it was posted under Idle?

    and having videos embedded in the fucking article?

    It's called 'convenience'. You may not appreciate it, but most people do. In fact, I think Slashdot should do so far more often.

    it's fucking '70s "artsy" too

    While I, myself, am no fan of the style either, I don't think it's the video's content that is the reason for its posting.

    this was not enabled by the new gen web techniques. this is shit.

    I wouldn't know - it's apparently a "This site works best with (read: only with) Google Chrome". Can't be bothered to install it.

    also, they're not a sensation

    They may be riding the momentum from back when they very much were (you know, the treadmill thing). if nothing else, many sites pick up on new 'Ok Go!' video releases because, as mentioned above, it's always something rather different from what you'd usually see. As such, perhaps 'sensation' is too strongly worded, but it captures the general idea.

    there's a fucking nintendo 3ds advert there.

    It's called AdBlock (or one of various alternatives) - you might want to look into it.

    You seem very angry - I don't know why, it's not like you're all that new here.

  6. Arcade Fire's was better and why HTML5? by Chetti · · Score: 5, Interesting

    I like Ok Go, They have an interesting way of using non-cgi to make interesting music videos... however looking at this video from a technical project standpoint... do the browser features (aka: HTML5) really add anything to this video? Don't get me wrong, the capabilities of the browser are really neat, and I bet it was quite the project to put this together. But, the technology doesn't really add anything visually to the video. It just stacks windows next to and on top of each other... might as well skip the multiple windows and just create frames or for that sake, just have them in a single video... I think Arcade Fire's video at http://www.thewildernessdowntown.com/ was a lot more interesting and a lot better use of web-tech. For one, it used Google maps data in a little more interesting of a way than simply writing out your message w/ feet. Also, they were able to use single backdrop with objects popping up in windows in different areas rather than just a matrix of windows playing a different video stream.

  7. Google is evil. RMS was right. by recrudescence · · 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 ... :(

  8. Not a good sign... by MaWeiTao · · Score: 2

    The video and music are far from the worst thing I've ever seen. I mean, compared to the current state of American pop music this is high art. That said, this feels like pop music for people who like to pretend they don't like pop music.

    And what happened with HTML5 being an open, cross-platform standard? I thought we had seen the last of browser-specific websites. Either the developers were too lazy to ensure this worked in all browsers or, far more likely, they were pushed into making this Chrome only. Either way, it doesn't bode well for HTML5 at all especially if companies are going to start offering proprietary variations.

    It's probably not good for the future of Chrome either. Microsoft could get away with it because they already had massive market share by the time this sort of thing started happening. And at the time it happened mostly because developers couldn't be bothered to support other browsers.

    1. Re:Not a good sign... by PieSquared · · Score: 2

      "And what happened with HTML5 being an open, cross-platform standard"

      Nothing. It's just that so far nobody has a complete implementation, and different browsers have different parts working. At the moment it appears Chrome is the furthest along, and they're pushing people to use their working subset of HTML5 to the fullest with the whole "chrome experiments" thing. The others will catch up eventually.

      --
      Does a line appended to your comment give your post meaning in and of itself, or only in relation to those without?
  9. WHO?? and Why?? by luckymutt · · Score: 4, Interesting

    Who the fuck is "OK Go" ??
    And why /. running an advert for them?

    Also, their crappy site 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.

    "Recommend" ?? Bullshit. It won't let you see it in any other browser. That's not recommending.

    In summation, a mediocre artsy group released a shit video using an HTML5able codec so they can be whored around by Google to get a greater browser market share.

  10. Bottom left side of the page by __aaqvdr516 · · Score: 4, Insightful

    "This is a Chrome Experiment"

    and this is me closing the page *click*

  11. Re:sorry, shitty band. by dyingtolive · · Score: 3, Interesting

    Does the constant hate ever get exhausting? I mean, I know it's trendy nowadays, but it wears me the fuck out.

    --
    Support the EFF and Creative Commons. The war is coming, and they're supporting you...
  12. I don't know... by PopeRatzo · · Score: 2

    I'm not saying this video is gay, but Marcus Bachmann says it's "fabulous".

    And he shits Frogurt, so draw your own conclusions.

    --
    You are welcome on my lawn.
  13. Hmph. by gh0st1nth3mach1n3 · · 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*

  14. Sorry, not playing here. by jht · · Score: 2

    It's a cool idea and the YouTube video is neat, but requiring Chrome? Non-starter. I'm sure it's because they're pushing WebM video out, and so it's just another shot in Google's War On Apple (the WebM vs. H.264 battle again). No thanks. I use Chrome on occasion, but I refuse to use websites that require one specific browser even when it's supposedly up to standards.

    Last summer when Arcade Fire did their Chrome Experiments video (the interactive film for "We Used to Wait"), it rendered really well on Safari and Chrome, OK on prerelease Firefox builds, and not really on IE8, but that was because it really was built in HTML5 and made concerted efforts to be neutral.

    --
    -- Josh Turiel
    "2. Do not eat iPod Shuffle."