2009-07-01 [17:38:00.0000] gah, it's too warm to sleep [01:00:00.0000] http://stackoverflow.com/questions/1038191/google-homepage-not-valid-html/1044778#1044778 [01:33:00.0000] depending on how the page is built, I'm quite sure the performance of google could actually be improved by adopting a more standards based approach [01:33:01.0000] I feel guilty for posting on the codec thread [01:33:02.0000] I should have known better [01:34:00.0000] othermaciej: I can't see what part of your message somebody could reasonably take issue with. [01:34:01.0000] I think the hardware concern is a major concern [01:35:00.0000] MikeSmith: I was just hoping that I wouldn't extend the flamewar [01:42:00.0000] othermaciej: if you didn't post on the thread at all, your silence would be interpreted as a clear indication that you are indeed part of the conspiracy [01:42:01.0000] obviously [01:43:00.0000] I think it's high time I added some H.264 and Theora stuff to my wisdom generator [01:47:00.0000] heh. looking at it now, I see that I already had the "the MP/LA Expert Group" in there [01:47:01.0000] under the category "seemingly-benign-pawns" [01:56:00.0000] ok, now with even more wisdom: http://logopoeia.com/wisdom/ [01:56:01.0000] well, slightly more [01:58:00.0000] first hit: "the divine principle of time inequality is encoded in Anne van Kesteren's weblog." [01:58:01.0000] though reading further it also says "the divine principle of time inequality is encoded in the Nag Hammadi Library" [01:59:00.0000] "Eminent thinkers throughout history (Roy Fielding, etc.) agree that the divine principle of time inequality is the transcendental principle behind all creation" :p [02:10:00.0000] is any spec responsible for XMLSerializer? [02:13:00.0000] nope [02:15:00.0000] :-( there should be [02:16:00.0000] It turns out that MySpace uses it on HTML DOMs and makes expectations [02:16:01.0000] maybe XMLSerializer and DOMParser can be snuck into Web DOM Core [02:16:02.0000] what expectations do they have? [02:18:00.0000] othermaciej: they expect no generated namespace declarations [02:18:01.0000] where do they depend on that? [02:19:00.0000] I think Safari would generate namespace declarations and so violate their expectation [02:19:01.0000] they except h=h.replace(/|<\/html>|/gi,"") to zap the root element tags [02:19:02.0000] when updating status/mood [02:21:00.0000] you're making it sound like their way to do status updates is a Rube Goldberg device [02:25:00.0000] othermaciej: it is [03:10:00.0000] if we want an good baseline video codec [03:10:01.0000] and the barrier is the choices made by device manufacturers and their hardware suppliers [03:10:02.0000] and their decisions are purely economic [03:11:00.0000] how varied are the DSPs used in contemporary handhelds? [03:11:01.0000] then the only practical way forward is to encourage the proliferation of content in an unencumbered codec, to tip that economic balance [03:12:00.0000] so it seems to me that everyone who's interested in having a good baseline video codec should be encouraging that [03:13:00.0000] including by supporting Theora wherever the device constraints do not apply [03:15:00.0000] hsivonen: a lot are using these OMAP chips, but a lot aren't [03:16:00.0000] just wondering if writing for a Nokia shipped TI chip results in any portability to whatever Apple uses in iPhone [03:16:01.0000] I believe the answer is no [03:17:00.0000] ok :-( [03:42:00.0000] oh hey, gsnedders just invaded my inbox via our bug tracking software [03:42:01.0000] welcome! [03:45:00.0000] annevk2: I already made your point about vendor consensus! [03:46:00.0000] therefore it's a good one :-) [03:46:01.0000] is Web DOM Core a W3C deliverable already? [03:47:00.0000] annevk2: mwhaha? [03:49:00.0000] roc, teaches me to read the whole thread first (over and over again...) :) [03:49:01.0000] this is why gmail is superior [03:52:00.0000] /me hasn't read the whole thread but points out that Nokia ships Flash on Maemo [03:52:01.0000] /me wonders what *that* does to battery life when watching YouTube [03:52:02.0000] I guess I should measure [04:21:00.0000] roc, congrats btw on Firefox 3.5, haven't tried the official release yet, but it sure seems like a great product [04:31:00.0000] thanks [04:34:00.0000] but 3.6prealpha1 is what the cool kids are using these days :-) [04:35:00.0000] so I hear, with a certain pref turned on rather than off :) [04:36:00.0000] roc: what exciting stuff is planned for firefox.next? [04:38:00.0000] Henri's HTML5 parser is on trunk, I assume that's what Anne was referring to [04:38:01.0000] hopefully we'll turn it on for FF.next [04:39:00.0000] well, I'm sure we'll turn it on, the question is whether we'll turn it off after we see what it does to the Web :-) [04:39:01.0000] hehe [04:39:02.0000] multiple backgrounds is already on trunk [04:39:03.0000] is there anyone looking at webforms stuff? [04:40:00.0000] someone is looking at file upload [04:40:01.0000] I'm not sure what that plan is [04:41:00.0000] Jonas is working on XBL2, I suspect we may try to build new web forms stuff on top of that [04:41:01.0000]