Slashdot Mirror

← Back to Domains

Domain: lachy.id.au

Stories and comments across the archive that link to lachy.id.au.

Comments · 7

  1. Re:So let's see: by BZ · · Score: 3, Informative · on VP8 Decoder Implemented In Flash Using Alchemy

    http://lachy.id.au/log/2010/05/webm under "Benefits of Matroska" describes the seeking issues in some detail. The summary is that ogg requires you to read more separate bits to seek correctly, and each separate bit ends up having to be a separate HTTP request in the context of web streaming. So your latency starts to bite you when seeking. It's not an issue if you don't have to seek or if you have the whole file already. But for the youtube use case, neither is true, typically.

  2. Who supports the VIDEO tag with Ogg Theora anyway? by ivoras · · Score: 1 · on YouTube, HTML5, and Comparing H.264 With Theora
    Is Firefox 3.5 the only browser currently supporting the VIDEO tag with the Ogg Theora codec? Here's what I can see on recently installed browsers:
    • FF 3.5 beta: OK
    • Google Chrome 2: NO
    • Opera 10 beta: NO

    Here's a very simple test page: http://lachy.id.au/dev/markup/tests/html5/video/003.html .

  3. Re:Lethargy.com by Lachlan+Hunt · · Score: 1 · on HTML to be 'Incrementally Evolved'

    Actually, it take a whole lot more effort than that. There's a whole heap of issues regarding MIME types, character encodings, style sheets, scripts, well formedness, entity references and much, much more. See XHTML is not for Beginners.

  4. DOM 2 Events by AKAImBatman · · Score: 5, Interesting · on Quiz Microsoft's IE Team Leader

    One of the stated purposes of IE7 was to better support the W3C standards, and (presumably) to increase compatibility among W3C-compliant browsers. Yet despite multiple requests for DOM 2 Events support, the IE team decided to overlook this support. Currently, IE is the only major browser lacking DOM Events support. Which is a major issue, as IE's attachEvent() design means that special code must be written for IE compatibility.

    As someone who's been forced into using runtime patches (example) to increase IE's compatibility with DHTML code, I feel compelled to ask: Why has the IE team ignored this critical standard?

  5. Missing - DevEdge Sidebar by JPyObjC+Dude · · Score: 4, Informative · on Migrating IE Web Apps to Mozilla

    Unfortunately, the IBM doc is missing a good description of the DevEdge sidebar which is available at:
    http://lachy.id.au/dev/mozilla/sidebar/sidebar.xul

    DevEdge toolbar is the perfect tool to link to often buried resources on the w3c website. It is ok for JavaScript but that, a good book is always a good idea:
    http://www.oreilly.com/catalog/jscript3/

    JsD

  6. Two Apps and Two Extentions by JPyObjC+Dude · · Score: 1 · on Best Web Authoring Application?

    Text Editor (Ultra Edit on Windoze)
    Mozilla (the firefox kind)
    Dev Edge Sidebar Personally, I don't wysiwyg. Code is simply too bulky. Better to code the hard way. You will really know how to code that way anyhow. Throw in Mozilla Web Developer ext and you are laughing :] JsD IE == WhyE

  7. Re:Is the result valid HTML/XHTML? by ubernostrum · · Score: 1 · on Google Cans Comment Spam

    Google is doing this the right way. They went back and read the HTML specification to see if it was already capable of doing what they needed. It does? Great! Let's utilize the standard!

    I'd actually argue that Lachlan Hunt was the one who read the standard; he's the first person I know of who suggested something like this.