00:11
<Dashiva>
"First of all, it's not like this code needs to be maintained *once*, it needs maintenance every time the set of void elements change. I would call this a stupid design of the target language."
00:11
<Hixie>
we did learn about particle and anti particles in undergrad
00:11
<Dashiva>
I'm tempted to reassign the "stupid design" tag to whoever decided it was a good idea to output HTML with XSLT :)
00:12
<Hixie>
can't recall if the hawking radiation was part of the discussion though
00:12
<Hixie>
anyway, bbl
00:14
<Lachy>
jgraham, what is it about particles and antiparticles that is a lie?
00:15
<Lachy>
Is it just the fact that the antiparticle is also a particle, just with opposite charge (or something like that)?
00:16
<annevk>
Dashiva, yeah, I don't really get why we need to fix HTML5 while they really want to fix IE...
00:17
<BenMillard>
jgraham, I'm redesigning the test file table to see if our views on that making it better are true or not
00:18
<Lachy>
BenMillard, did you get that table I emailed you? Have you had a chance to investigate it yet?
00:19
<Dashiva>
National Enquirer: Dave Hyatt spotted in Memphis supermarket
00:20
<roc>
Lachy: it's not that it's a lie exactly ... the truth is a bunch of mathematics. Then to explain it to people, the physicists have to say something which is an English approximation to the mathematics. And the approximation is necessarily rough.
00:20
<BenMillard>
Lachy, checking inbox now
00:20
<BenMillard>
Lachy, oh you mean the search result table? Yeah, I got it.
00:20
<annevk>
Dashiva, :p
00:22
<BenMillard>
Lachy, I filed in my "Research" folder for now.
00:25
<BenMillard>
Lachy, summary="Post query results" stood out as being text which would be better in <caption> or just omitted, since there's a preceeding heading which says "Displaying 1 to 50 of 854 reports"
00:27
<Lachy>
how do the various header algorithms deal with the dual-row items, each grouped by its own tbody?
00:28
<BenMillard>
Lachy, some header cells aren't using <th>, but if they were then parts of it would work
00:28
<jgraham>
Lachy: Nothing. I meant as an explaination for Hawking radiation
00:29
<Lachy>
in a way, it seemed much like a demo table I presented once before with a similar dual-tr structure. http://lachy.id.au/dev/2007/table-headers.html
00:30
<BenMillard>
Lachy, that table you just linked to is badly designed in several respects, imho.
00:30
<BenMillard>
it uses 2 levels of column headers but they don't make sense stacked up like that
00:32
<BenMillard>
the header cells and each row of data can be flatted to 1 row each, making it into a regular table that works without with plain <th>
00:32
<BenMillard>
Title Last Name First Name Middle Name Date of Birth Mailing Address City Zip Code
00:33
<BenMillard>
erm, "Title; Last Name; First Name; Middle Name; Date of Birth; Mailing Address; City; Zip Code"
00:34
<BenMillard>
an interesting thing in the query table, which the "smart colspan" step handles, is what I call "sectional headers"
00:35
<Philip`>
roc: Perhaps for physicists to explain it to themselves, they have to say something which is a mathematical approximation to the reality, and that approximation is necessarily rough
00:35
<BenMillard>
these are cells which colspan the entire width of the table, creating implicit sections but where the main headers at the start of the table must still penetrate
00:35
<BenMillard>
Lachy, for example (if it were using <th>): <td colspan="6"> 29 Aug 2008 </td>
00:35
<roc>
that's not how it works
00:37
<BenMillard>
Lachy, much like the table you linked to, the search query table is packing information into cells where it isn't logical to put it
00:38
<BenMillard>
Lachy, refreshing to see it using <li> for pagination links, though :) It follows a common design pattern for their order and delinks current location, which is all cool.
00:40
<BenMillard>
Lachy, it uses <tbody class> to avoid lots of presentational markup. neat
00:41
<BenMillard>
Lachy, it contains unlabelled checkboxes (sad and much more common than labelled checkboxes for things like this, from what I've seen)
00:42
<BenMillard>
Lachy, the alt text is sensible and useful on the whole. :)
00:42
<BenMillard>
Lachy, <a href target="_blank"> :(
00:49
<Lachy>
BenMillard, that table I linked to was actually designed by the designer of a project I was working on, cause it needed to have all that information fit into a narrow space that wouldn't handle having it all in a single row
00:52
<Lachy>
I didn't notice the target=_blank. Since I have support for that disabled in my browser, it never really bothers me in practice, unless the site actually depends on the new window opening for some functionality
00:55
<BenMillard>
Lachy, I set mine the same way. :)
00:56
<BenMillard>
Needing to cramming too much data into too little width is a fairly common problem...I often come across it in my day job as a website developer.
00:56
<BenMillard>
my favoured solution is to cut the data down so only the most useful stuff is shown, then it usually fits
00:57
<BenMillard>
(sometimes linking each entry to a page where all the rest of the data is available)
00:57
<Lachy>
yeah, that's what I try to do. But when I'm not in control of the content, and I just have to implement what the client wants, there's little I can do
00:57
<BenMillard>
Lachy, that's also an experience I share. :(
00:58
<BenMillard>
right, time for dinner...probably return in ~1 hour
01:00
<Lachy>
hmm, it seems that of all the media players I have, trying to find one that supports playing MKV that contains 2 1080p VC-1 video tracks and 5 AC3 audio tracks, and has UI for selecting which of those tracks to play, is a lot harder than I thought it would be :-(
01:00
<Philip`>
Even VLC?
01:00
<Lachy>
VLC doesn't support VC-1
01:00
<Lachy>
yet
01:01
<Lachy>
QuickTime might work, but with the Perian plugin, it takes forever to finish loading MKV videos, and while it's loading, it's having trouble playing the HD
01:04
<Lachy>
I suppose I should just remux them into separate files, one for each video track. Though it's a full quality blu-ray rip and I wanted to have it all self contained in one.
01:05
<Lachy>
Zoom player seems to work on windows, but it has some bugs
01:06
<GregHouston>
I haven't had much luck with MKV in general. It's probably user error, but I tried it out a couple times about 6 months apart with 3 different media players and an assortment of MKV files. My playback was always choppy and the audio was out of sync.
01:07
<Philip`>
You could buy a Blu-Ray player and the movie disc instead :-)
01:08
<Lachy>
Philip`, you're assuming I actually have the disc :-)
01:08
<GregHouston>
Indeed. :)
01:08
<Philip`>
Lachy: That's why I said "buy" :-p
01:09
<Lachy>
oh, ok. I thought you just said to buy the player
01:09
<Philip`>
I used the word "and", to indicate that I meant both :-)
01:10
<Lachy>
I'll get a blu-ray player from Australia when a) I get confirmation that the manufacturer is legally required to sell in region free (or at least provide RPC-1 firmware on request), and b) blu-ray drives are available for Mac, and c) I can afford to replace my current Macs
01:11
<Philip`>
So in the meantime, you deserve to get everything for free? :-)
01:11
<Lachy>
I'm fairly sure (a) is true, because of the Australian trade practices act and a nice court case that ruled it illegal for DVDs
01:13
<Lachy>
no, I pay $20 a month for my usenet subscription and even more for my internet connection. It's just that my money isn't going to the movie studios until they start showing that they want to treat their customers fairly
01:13
<Lachy>
I would buy more movies legally from iTunes instead, but they're really low quality compared to what I can get elsewhere
01:14
<Lachy>
and there's limited selection
01:15
<GregHouston>
The quality is generally good enough for me on Itunes, and so if I can rent it there I do, but most of their new releases are purchase only, which then sends me to usenet, and they lose out on my rental.
01:15
<gsnedders>
annevk: First comment is moderated
01:15
<gsnedders>
annevk: Approved
01:16
<Lachy>
GregHouston, I refuse to rent from iTunes because it's not possible to strip the DRM from those, whereas its easy to do from purchases
01:16
<Philip`>
Why is it unfair that they are offering their product (which you clearly want to consume) in various media (DVD, Blu-Ray, iTunes, etc) with various quality and limitations and price?
01:17
<Lachy>
Philip`, the DRM is unacceptable, especially the region encoding if it's done in the firmware instead of just software.
01:17
<jcranmer>
are people here using alt.binaries?
01:17
<jcranmer>
:-)
01:17
<Lachy>
jcranmer, yes
01:17
<GregHouston>
Lachy: I can see that. It's not much of an issue for me, because I watch everything on the same computer, don't own a tv, and most movies I will never watch a second time.
05:32
<BenMillard>
I've sent an e-mail requesting peer review of a follow-up to my last headers+id reply. Off to sleep now. I'll check the logs and my inbox when I return, just in case. :)
06:28
<Hixie>
http://lists.w3.org/Archives/Public/www-archive/2008Sep/0000.html is interesting
06:29
<Hixie>
if you look at it more closely:
06:30
<Hixie>
Sent Recvd Ratio Subjects Sent/Subj Author
06:30
<Hixie>
136 109 0.80 89 1.53 Ian Hickson
06:30
<Hixie>
66 57 0.86 30 2.20 Julian Reschke
06:30
<Hixie>
53 62 1.17 27 1.96 Henri Sivonen
06:30
<Hixie>
56 36 0.64 13 4.31 Boris Zbarsky
06:30
<Hixie>
39 36 0.92 14 2.79 Philip TAYLOR
06:30
<Hixie>
45 26 0.58 14 3.21 Leif Halvard Silli
06:30
<Hixie>
(these numbers are sorted on the total sent+recvd, not just sent)
06:31
<Hixie>
note the Subjects line :-)
06:50
<Hixie>
there, sent a reply with my version of the stats :-)
07:20
<hsivonen>
Hixie: interesting development in ratios since http://junkyard.damowmow.com/291
07:21
<Hixie>
people ignoring me more, you mean? :-)
07:23
<hsivonen>
Hixie: no, the people whose ratio is > 1.0
07:26
<Hixie>
heh
08:21
<hsivonen>
So YouTube conflates accessibility captions and translation subtitles under a "CC" menu
08:22
<Hixie>
stats for all time http://junkyard.damowmow.com/342
08:23
<Hixie>
if anyone has the complete whatwg archives in mbx format i can do the same for whatwg
08:24
<hsivonen>
I thought lists.whatwg.org had the complete archives. what's missing?
08:24
<Hixie>
the mbx format part
08:24
<Hixie>
afaik
08:24
<hsivonen>
ah
08:28
<hsivonen>
hmm. RB has sent more email than I have...
08:29
<Hixie>
oh hey
08:29
<Hixie>
the text files in the whatwg archives ARE mbx format
08:45
<Hixie>
http://junkyard.damowmow.com/343
08:45
<Hixie>
http://junkyard.damowmow.com/342 is public-html from the start
08:45
<Hixie>
http://junkyard.damowmow.com/343 is whatwg from the start
08:46
<Hixie>
whatwg has had over 700 people contribute ideas, wow
08:46
<hsivonen>
hmm. I've sent a lot of email :-(
08:46
<Lachy>
Hey, I made the whatwg list twice :-)
08:47
<Hixie>
hsivonen: for a while, you had the #1 spot in terms of outstanding e-mails on my list
08:47
<Hixie>
i think you're #2 now
08:47
<hsivonen>
Hixie: who's #1 now?
08:47
<Lachy>
Hixie, if you combine my @lachy.id.au and @iinet.net.au emails into one, how do I score?
08:49
<Hixie>
let's see
08:50
<hsivonen>
hmm. Juan R's Sent/Subj...
08:51
<Hixie>
a high sent/subj means one of three things as far as i can tell:
08:51
<Hixie>
1. you aren't explaining yourself well
08:52
<Hixie>
2. you're repeating yourself
08:52
<Hixie>
3. i'm responding to each e-mail individually instead of doing one mass e-mail
08:52
<Hixie>
(#3 probably only applies to me :-P )
08:53
<Hixie>
ok reload 343
08:55
<Hixie>
so in about a third of the time, public-html received about the same amount of mail
08:55
<Hixie>
that's insane
08:57
<Lachy>
Hixie, both lists have been high volume recently. I haven't been able to keep up with them.
08:57
<Lachy>
the whatwg list got to about 500 unread mails in my folder, mostly thanks to that RDF thread :-(
08:57
<Hixie>
yeah i tried to damp down the rdfa discussion when it got too verbose
08:58
<Lachy>
I suppose I should try to read them one day, but I mostly ignored it since I don't like RDF
08:59
<Hixie>
well the issue isn't really rdf
08:59
<hsivonen>
Hixie: what's the issue in your view?
09:00
<Hixie>
the issue is how do we address the needs of the communities that RDFa is addressing, and whether doing so is appropriate given our overall goals
09:00
<Hixie>
i need to look at some of manu's and ben's e-mails more closely to determine the answer to both
09:00
<Hixie>
but that will have to wait until after wf2
09:01
<Hixie>
(underlying both of those points is "what are the needs of the communities that RDFa is addressing")
09:05
<hsivonen>
to the extent the needs include compatibility with the RDF data model, it's about RDF
09:08
jgraham
suspects the RDF data model is too hard for mass adoption
09:17
<Hixie>
hsivonen: i don't think that's actually been listed as a need
09:20
<Lachy>
AFAICS, everything beyond rel=license is totally unnecessary verbosity when it comes to expressing copyright info.
09:22
<Hixie>
i'm not even convinced rel=license is needed
09:22
<Hixie>
it's only needed if the copyright info is going to actually be used by computers
09:22
<Hixie>
and i'm not convinced that it is
09:27
<hsivonen>
Hixie: one of the reasons why I chose Flickr was that Flickr is the place people go to when they want to search for CC-licensed photos
09:27
<hsivonen>
Hixie: they don't go to Google image search
09:28
<hsivonen>
there is value in being able to search by license
09:28
<jgraham>
hsivonen: Would it work well in an open system?
09:29
<jgraham>
It doesn't work all that well on flickr
09:29
<hsivonen>
jgraham: it would not work if people can make licensing claims cross-Origin about other people's works
09:29
<hsivonen>
jgraham: but it could work it the licensing info is near the data object
09:29
<hsivonen>
preferably inside it
09:30
<hsivonen>
jgraham: what sucks on Flickr is that people don't know what they are doing when the flip the defaults
09:31
<jgraham>
hsivonen: Inside might work technically but I think user-invisible metadata outside the object would almost never be right
09:32
<hsivonen>
jgraham: also, what sucks is that people take photos of people, CC doesn't deal with model release, and the photographer can't unilaterally concoct model release
09:32
<jgraham>
hsivonen: People not knowing waht they are doing would be even worse without a consistent UI that explained everything, right?
09:32
<hsivonen>
jgraham: could be
09:32
<hsivonen>
I don't think Flickr's UI explains everything, though
09:32
<jgraham>
hsivonen: AFAIK Model release laws vary wildly by country
09:34
<hsivonen>
Flickr says "You can choose to use a Creative Commons license to allow more liberal use and sharing of your photos or video while still maintaining reasonable copyright protection."
09:34
<hsivonen>
one could argue that "reasonable copyright protection" is not a good UI term
09:36
<jgraham>
hsivonen: Yeah, the explaination is worse than I remembered
09:36
<Lachy>
Does flickr default to a CC licence or ordinary copyright?
09:36
<hsivonen>
Lachy: defaults to ARR
09:36
<Lachy>
ok
09:36
<jgraham>
Lachy: A CC default would be disaterous
09:37
<jgraham>
Lachy: Lots of photog. types are seriously paranoid about any copying
09:37
<Lachy>
jgraham, yeah. But that means that people are somehow being coerced into changing to a CC licence, without actually understanding the concequenses of their actions
09:38
<jgraham>
e.g. http://duncandavidson.com/2008/04/the-copyright-conspiracy.html
09:38
<hsivonen>
Lachy: CC and FSF have very different marketing
09:39
<jgraham>
Lachy: In what sense coerced? They are given several options but none are presented as "better"
09:39
<annevk>
Hixie, did you add fora⊙an to annevk⊙oc?
09:39
<annevk>
(for the WHATWG list)
09:39
<hsivonen>
annevk: looks like it
09:42
<Hixie>
hsivonen: google has cc search that is directly based on the cc metadata; what is your opinion of it?
09:42
<hsivonen>
Hixie: too well hidden
09:42
<annevk>
Hixie: 3095, Anne: 904, Henri: 590
09:42
<annevk>
I should e-mail less :)
09:43
<annevk>
whoa, Matthew and Jim Ley make it to the top five
09:43
<Hixie>
annevk: the script automatically merges names that are the same
09:43
<Lachy>
jgraham, coerced is probably the wrong word. I probably should have said tempted or something, because there are people with CC-licenced stuff on flickr who still complain when their stuff gets reused
09:43
<hsivonen>
Hixie: also, not available in image search
09:43
<Hixie>
annevk: note that the script does things based on time active, so unless jim posts again, he'll stay high
09:44
<Hixie>
hsivonen: well there's no way with rel=license to label an image
09:44
<Hixie>
hsivonen: so if that's your use case, rel=license won't help google
09:44
<hsivonen>
Hixie: yeah. that's a problem.
09:44
<Lachy>
that copyright conspiracy article is interesting. But in which countries does any form of copyright registration apply? Is that just a US thing, or more widespread?
09:44
Hixie
shrugs
09:44
<Hixie>
if you say so
09:44
<Hixie>
:-)
09:44
<hsivonen>
Hixie: I want a way to have a license field in EXIF/JFIF/PNG
09:44
<hsivonen>
Hixie: and then I want tool support for it
09:45
<Hixie>
hsivonen: ah well that's not my problem, luckily
09:45
<hsivonen>
Hixie: It annoys me the CC isn't standardizing embedded license metadata for EXIF/JFIF/PNG/Ogg/MP4
09:45
<hsivonen>
and PDF in a simple way
09:46
<hsivonen>
Lachy: it's a U.S. thing
09:47
<jgraham>
You can register copyright in the UK
09:48
<jgraham>
Dunno how it compares to the US
09:48
<Lachy>
ok, that's what I thought. But I find it annoying that whenever I read anything related to copyright, it's usually very much US-centric
09:48
<hsivonen>
Lachy: you may safely omit "related to copyright"
09:48
<roc>
the US system gets exported everywhere else eventually
09:49
<Lachy>
so I basically have no idea what the copyright situation is in Australia, although I do know that we also have excessively long copyright terms
09:49
<roc>
say hello to WIPO
09:49
<hsivonen>
roc: It would be great if the U.S. system had been exported without the Victor Hugo input
09:49
<Lachy>
I think it's life-of-author+70 years, which is absolutely absurd
09:49
<hsivonen>
Lachy: that stuff came from Europe
09:49
<Lachy>
who's Victor Hugo?
09:50
<hsivonen>
the disaster is taking the worst parts of French and American copyright things and mixing them
09:50
<Lachy>
I wish we could go back to 14 year copyright terms
09:51
<hsivonen>
Lachy: a famous writer who was so annoyed at Americans pirating his books that he wrote what lead to the creation of the Berne Convention
10:16
<hsivonen>
Hixie: I think searching images by license is a more common use case than searching text by license, since images have different remixability characteristics
10:16
<Hixie>
no disagreement there
10:17
<hsivonen>
so in that sense, standardizing and implementing a license field for EXIF should be a higher priority than rel license
10:17
<Hixie>
agreed
10:17
<Hixie>
EXIF isn't my problem though
10:17
<Hixie>
:-)
10:24
<Lachy>
wow, Microsoft has just patented the page up/down keys http://news.zdnet.com/2424-9595_22-218626.html
10:25
<Hixie>
i try and avoid reading about patents
10:25
<Hixie>
companies become three times more liable to damages in the US if it can be demonstrated that they (or their employees) had knowledge of an infringed patent
10:26
<roc>
that's actually changing
10:26
<Hixie>
so it's better to be ignorant
10:26
<Hixie>
roc: oh thank god
10:26
<Hixie>
roc: for the better?
10:26
<roc>
depends on your point of view, but yeah
10:26
<Hixie>
good to hear
10:29
<Lachy>
I only read about patents that get mentioned on places like /., and are so absurd that there's obviously plenty of prior art
10:30
<Hixie>
like the Eolas patent?
10:30
<Lachy>
yeah
10:30
<roc>
oh, the Patent Reform Act 2007 is stalled :-(
10:30
<Hixie>
lachy: being absurd and having plenty of prior art doesn't seem to matter
10:30
<Hixie>
roc: :-(
10:31
<hsivonen>
for some reason, people like the concept of Trial by Jury despite cases like Eolas
10:31
<Hixie>
and people like spec design by consensus despite cases like XLink
10:32
<annevk>
some people even like XLink
10:33
hsivonen
notes that the WHATWG is closer to arguing things to a professional judge and a panel of semi-pro lay judges than to Trial by Jury
10:33
<Hixie>
yup
10:34
<Lachy>
hsivonen, what about public-html?
10:34
<Philip`>
Lachy: They're not patenting the keys at all - they're patenting a method of scrolling (which jumps in a one-page increment and preserves the vertical offset of your view of your page, regardless of zoom, etc), which might be triggered by those keys
10:34
<Hixie>
(using the term professional to mean literally "paid", as opposed to "competent")
10:34
<hsivonen>
Lachy: no comment
10:34
<Lachy>
Philip`, yeah, I realised that. But I just summarised it poorly
10:35
<hsivonen>
(using semi-pro to refer to the Finnish trial system--not the proness of the WHATWG panelists)
10:36
<Philip`>
Lachy: ZDNet summarised it equally poorly/inflammatorily :-)
10:36
<Lachy>
Philip`, in any case, that method of using pg up/dn has been used for decades
10:37
Philip`
can't easily remember any programs that scroll like that
10:41
<Lachy>
Philip`, web browsers, word processors, text editors, etc.
10:41
<Lachy>
they all scroll like that
10:41
<Lachy>
Linux man pages even
10:41
<Philip`>
Web browsers and text editor don't usually split the document into pages
10:42
<Philip`>
Word processors scroll by roughly the viewport height (which depends on your zoom setting), not by a single page
10:43
<Lachy>
in the case of web browsers, since a web page is a continuous medium, a "page" could be considered equivalent to the content of the viewport
10:43
<Lachy>
no matter how high it is
10:43
<Philip`>
If you're looking at just the top of a page, and press page-down, you jump to the bottom of page, whereas the patent is talking about jumping to the top of the next page
10:44
<virtuelv>
Philip`: @media projection
10:44
<Lachy>
Philip`, Print Preview
10:44
<Philip`>
Lachy: Uh, you can't just consider things to be things that they aren't, and say it's prior art :-p
10:45
<Lachy>
Philip`, the patent is too broad
10:45
Philip`
tries print preview in Opera and Firefox, and in both cases it scrolls by the zoom-dependent viewport height and not by a single page
10:45
<virtuelv>
Philip`: and virtually any other slideshow tool
10:46
<virtuelv>
Any PDF viewer whose zoom is set to "Fit to window" or similar
10:46
<virtuelv>
man
10:46
<Hixie>
Lachy: the patent is a software patent, it's a given that it's not a good idea. but lots of companies have software patents, microsoft is no exception.
10:46
<Hixie>
virtuelv: apple's pdf viewer doesn't do what this patent says, i just checked
10:48
<virtuelv>
Hixie: evince does, if set to "Best fit"
10:48
<virtuelv>
Acrobat reader has a similar means
10:49
<Lachy>
even Notepad scrolls like that (though, I'm aware its an MS program, it's been around for years, and to patent the process now is just absurd
10:49
<Philip`>
virtuelv: That only works because the viewport height happens to be the height of a single page
10:49
<Philip`>
Lachy: Notepad doesn't have pages
10:50
<Lachy>
Philip`, define what a page is?
10:51
<Philip`>
Lachy: A page is like a rectangular piece of paper, but on a computer
10:51
<Lachy>
if you're only talking about the on-screen representation of an A4 page, then ok. But that's irrelevant, since the concept of keeping the cursor in place on screen and shifting it down by the viewport has been around forever
10:52
<Philip`>
The point is not to shift it down by the viewport - the point is to shift it down by a page, regardless of the viewport
10:52
<Hixie>
the whole point of this patent as i understand it is that it isn't about shifting by the viewport but shifting by the page height
10:52
<Hixie>
and i think virtuelv is right that acrobat does that, i remember it driving me crazy
10:54
<virtuelv>
either way, patents are just Evil
10:54
<Hixie>
patents as originally defined make some sense
10:55
<virtuelv>
Hixie: yes, but the problem is that the patent system does not scale
10:55
<Hixie>
if you come up with an idea for a physical product, it makes sense to give you some protection to allow you to sell it before some big multinational can use your idea and destroy your margins
10:55
<virtuelv>
and the threshold for getting a patent is ridiculously low these days
10:55
<Hixie>
but i agree that at least for software it makes no sense
10:56
<virtuelv>
like that guy getting a patent for a special case of multiply-linked lists
10:56
<Hixie>
because the economics just aren't the same for software
10:56
<Hixie>
patents on methods of construction or on algorithms, etc, also make no sense imho
10:58
<virtuelv>
a friend of mine with a PhD in control systems theory says most of the patents she encounters are also complete bullshit
10:58
<virtuelv>
and obvious to anyone skilled in the trade
10:58
<Philip`>
What about e.g. the MP3 algorithm? That presumably took substantial effort to develop, and seemed far in advance of any alternatives at that time, and the patent was specific enough that it didn't prevent development of similar competitors like Vorbis
10:58
<virtuelv>
(mostly for industrial processes, AIUI)
10:59
<virtuelv>
Philip`: discovering the general theory of relativity also took substantial time and effort, and Einstein's theories were specific enough
10:59
<virtuelv>
should he have been granted a patent on it?
11:00
<virtuelv>
algorithms are discovered, not invented
11:00
<Hixie>
algorithms are invented
11:00
<Hixie>
and if the mp3 patent was awarded, then a patent on the algorithm for predicting time dilation should be too
11:01
<Hixie>
and probably would be
11:02
<Hixie>
Philip`: i could see an argument for that, if it was limited to a very small time frame (low single digit years), and was limited to people actually using the technology to make money
11:02
<Hixie>
Philip`: it shouldn't prevent me from writing an implementations and sharing it with people online
11:02
<Lachy>
Hixie, wouldn't that just be a mathematical equation, which can't be patented?
11:03
<Hixie>
Lachy: all software is "a mathematical equation" in the same sense
11:04
<Philip`>
virtuelv: There's only one theory of relativity, and even if it was phrased differently you'd get the same results, so that theory just needed to be discovered; but there are millions of ways you can encode audio, each slightly different, and the problem is choosing the right set of tradeoffs, so that's much more like invention than like discovery of a pre-existing thing
11:04
<Hixie>
there's not just one theory of relativity
11:04
<Hixie>
the whole point of how science works is that there are many theories on everything
11:04
<Hixie>
we test them to see which one is closest to reality each time
11:04
<Hixie>
and then keep improvign it
11:05
Philip`
tries to work out how to phrase it better
11:06
<Hixie>
coming up with an algorithm to predict how the universe will act is the same thing as writing an algorithm to compress music
11:06
<Hixie>
it just does something different
11:07
<roc>
no, I think there's a difference between science and engineering
11:08
<Philip`>
I think I'm trying to say something like how Newton's theory of gravity and Einstein's theory of gravity are substantially different, and there aren't a million theories in between that they could have just as easily decided on but that might not have worked quite so well in practice
11:09
<Hixie>
roc: what's the difference?
11:09
<Philip`>
Einstein didn't do some experiments to decide whether E=mc^2 or E=mc^2.01 or E=0.01+mc^2 - there's just one way that makes sense
11:10
<Hixie>
there's "just one that makes sense" in the same way that there is "just one" WebSocket spec definition that makes sense
11:10
<annevk>
lol, instead of volunteering to do something, TAYLOR starts debating Hixie's list, typical
11:11
<Hixie>
well my list had the desired effect
11:11
<Hixie>
someone (i won't say who in case they don't actually want to do it!) contacted me and volunteered to work on something maybe :-)
11:11
<Philip`>
The effect of demonstrating that people are more willing to complain about editors than to help as editors? :-)
11:12
<Hixie>
no, getting someone to volunteer
11:12
<Hixie>
at least if they're complaining about the list they aren't complaining about the spec, though
11:13
<Hixie>
happy mailman mailing list membership reminder day, btw
11:14
<Hixie>
haha pt(w)'s e-mail is funny
11:14
<Hixie>
let's see... i've written four specs like html5... he has written none... but hell, maybe he does know better after all
11:17
<Lachy>
I like how he challenged some of the requirements, without actually making a case against them
11:17
<Hixie>
my favourite has to be the last one:
11:17
<Hixie>
"a pragmatic attitude that is willing to put the needs of the users, authors, and implementors (in that order) far ahead of technical purity"
11:17
<Hixie>
...which he challenges
11:17
<Lachy>
ironically, he partially challenged the "the ability to defend a decision" one without actually defending his :-)
11:18
<Hixie>
well it makes sense that he wouldn't defend a decision to not defend decisions :-P
11:18
<Hixie>
that's not ironic that's just plain sensible :-P
11:18
<Philip`>
You should have added "The editor must not drown kittens" and see if anyone objected
11:19
<Hixie>
i didn't expect people to object!
11:19
<wilhelm>
Well, someone fulfilling those requirements would probably produce yet another spec he'd be unhappy with. Your axioms do result in a very specific type of spec.
11:20
<Philip`>
Maybe his view is the editor is just meant to edit, and decisions are made by WG consensus and not by the editor, and therefore the editor does not need to defend decisions
11:22
<roc>
in engineering we're optimizing a very complex utility function and we make a lot of trade-offs
11:22
<roc>
in science the utility function is much simpler, primarily "does this theory fit the data"
11:22
<roc>
and you make very few tradeoffs
11:22
<Hixie>
wilhelm: that's what i led with. "a spec of the quality of html5" or some such
11:23
<Hixie>
Philip`: that doesn't get you a spec like html5. :-)
11:23
<Hixie>
roc: i'll grant you that, but i'm not sure that changes the argument at the point of "is it patentable"
11:23
<Philip`>
Hixie: Many people may consider that to be a good thing :-)
11:24
<Hixie>
Philip`: probably :-)
11:25
Philip`
guesses consensus works best on specs which not many people care about, which is either boring specs that they're not interested in or new specs that they haven't heard of
11:25
<Hixie>
i don't know of any spec where consensus has worked well
11:25
<annevk>
it's hard to find such a spec, I tried
11:26
<Hixie>
i think the most i've found is specs where consensus didn't work worse than one poor editor would have
11:26
<Hixie>
and those were all very small specs, where there simply weren't that many design decisions to screw up
11:26
<Philip`>
Are there any specs were only one person was involved in development? That kind of spec would surely be the result of the unanimous consensus of all who were involved
11:26
<roc>
I think the idea is that in science, you're so constrained by observations that there's little creativity and so little """invention"""
11:26
<Philip`>
s/were/where/
11:27
<roc>
but don't ask me to defend the theory of patents
11:27
<Hixie>
roc: i think that relativity is very creative. and quantum even more so.
11:27
<Hixie>
roc: but yeah.
11:27
<Hixie>
Philip`: specs are really just software written in prose, and the same applies to both, really
11:27
<Hixie>
Philip`: you can't write good software in a committee
11:28
<roc>
actually I think you're wrong there. The observations force you to adopt those theories, or theories equivalent to those theories
11:28
<Hixie>
roc: the sheer number of competing GUTs right now suggests otherwise
11:29
<roc>
they're all "relativity + QM + extensions"
11:29
<Hixie>
roc: science works the other way around. You come up with many theories, then you make predictions using them, and only the ones that predict reality survive.
11:29
<Hixie>
roc: but you still have to come up with theories, and that's creative.
11:29
<roc>
and the fact that the extensions have so many degrees of freedom is in fact very disturbing to many/most scientists
11:29
<Hixie>
roc: it's a bit like having a test suite, and then writing a bunch of programs, and then throwing the ones away that don't pass the test suite.
11:30
<Philip`>
What do you do when you find there was a bug in the test suite?
11:30
<roc>
ok, but in engineering you get to choose the test suite and the results you want from each tests
11:30
<roc>
subject to rather vague and broad requirements
11:30
<roc>
in science, you don't get to choose the results
11:31
<roc>
and you're not supposed to be choosy about the tests either
11:31
<Hixie>
roc: the problem is mostly that the predictions are things we can't yet test (e.g. LHC should help with that), but once we get to the stage where practical physics is testing the theoretical stuff again, they'll go away.
11:31
<Hixie>
Philip`: science by definition has a bug-free test suite. :-P
11:31
<Hixie>
roc: granted
11:32
<Hixie>
roc: but i still don't think that difference is, or should be, relevant for the purposes of the patent system
11:34
<Lachy>
concensus definitely screws things up, especially when that concensus overrules the editor's decision
11:35
<Philip`>
More than when the editor's decision overrules the consensus?
11:35
<Lachy>
just look at the selectors api naming crap. People were happy with the names I chose. Then I got overruled, and people were disappointed
11:35
<Hixie>
the naming thing just made different people sad
11:35
<Hixie>
naming decisions are a pain and really should never be something that people have to vote on
11:36
<Philip`>
If people were happy, how was there consensus to overrule that decision?
11:36
<Lachy>
Philip`, there should be no concensus. In fact, in a really large group, concensus is almost impossible
11:36
<Philip`>
Lachy: Perhaps the solution is to avoid really large groups, not to avoid consensus
11:36
<Hixie>
there wasn't concensus in the case of the selector naming at any point iirc, it was just a bunch of narrowly-won votes that kept swinging the results back and forth
11:37
<Lachy>
Philip`, because it was decided by a vote, with each member ranking their preferences in order. The winner wasn't the most preferred by anyone, it just happened to have the highest average vote
11:37
<Hixie>
(there definitely needs to be some oversight of the editor, though)
11:38
<Hixie>
(i just think it needs to be oversight of the form "keep us happy enough or leave", not "keep us very happy or do what we say")
11:38
<Hixie>
(because that both gives more motivation to the editor, and more responsibility, and thus more care, from the oversight)
11:39
<Lachy>
I prefer "if you're not happy, you leave!" :-)
11:39
<Hixie>
well an editor with no oversight has nothing to keep him in check, and that's dangerous
11:40
<Hixie>
because it is supremely easy to go down a path where you think you're doing the right thing and you're ignoring people saying that you're not
11:40
Philip`
thinks someone should fork HTML 5, to promote some competitive spirit between the editors of each fork
11:40
<Hixie>
even when they're right
11:40
<Lachy>
that way, the editor is always happy and the only people left in teh group are those who agree
11:40
<Hixie>
Philip`: i'm definitely up for that
11:40
<Hixie>
Philip`: i totally agree that that would be a good thing (seriously)
11:40
<Hixie>
Lachy: that's how xhtml2 came to be, btw
11:40
<Lachy>
Hixie, I know :-)
11:41
<Hixie>
so i think it's not a good thing :-)
11:42
<Lachy>
Hixie, forking the spec wouldn't be good if the two diverged significantly and different implementations followed different specs
11:42
<Hixie>
they wouldn't
11:43
<Hixie>
at least, my copy of it would always follow what the UAs did
11:43
<Lachy>
what wouldn't? The specs significantly diverging, or the implementers following different specs/
11:43
<Lachy>
?
11:43
<Hixie>
the implementers following different specs in a way that resulted in lack of interop
11:44
<Lachy>
I suppose, since they generally try to follow each other
11:45
<Lachy>
so if the spec was forked, and both editors tried to equally follow what the implementers did, then by the end, we'd have 2 specs saying roughly the same thing in 2 different ways
11:45
<roc>
because of human error, the specs would say two subtly but very different things, and we'd be in hell
11:46
<Hixie>
i don't think you'd see the browser vendors following different copies of the spec
11:47
<Hixie>
i also don't think you'd find two people who'd edit the spec competently enough for the two to both be credible for long
11:47
<Hixie>
if they were both that competent, they'd likely get over their differences and merge
11:48
<Lachy>
anyway, from you're list, the things I need to work on are "the ability to defend a decision and resist flip-flopping" and "the ability to write tools to perform studies of Web content"
11:48
<Hixie>
you do need to resist flip flopping more. :-) but you're doing fine as editor
11:49
<Hixie>
the thing you actually need to work on is getting more editing hours in your day :-)
11:49
<Hixie>
s/need/would need/
11:49
<Lachy>
I would need to find an employer that would let me work on specs 100%
11:50
<Hixie>
or work in your free time
11:50
<Hixie>
having tried both, i recommend the former
11:51
<Hixie>
(getting an employer willing to let you work on specs 100%)
11:51
<Hixie>
assuming you want to become a full time editor, that is
11:52
<Lachy>
well, maybe not 100%, probably more like 80% to be reasonable, with 20% time on other random stuff
11:53
<Hixie>
good luck with that
11:53
<Lachy>
as long as I have 0% time assigned to filling out time sheets
11:53
<Hixie>
right now i'm at ~120% specs, ~10% internal stuff google wants me to work on
11:53
<Hixie>
and 0% other random stuff
11:54
<Lachy>
by random stuff, I meant including all the internal stuff the employer wants.
11:54
<Hixie>
ah
11:55
<Hixie>
html5.org is hammering svn.whatwg.org again
11:56
<annevk>
hmm
11:56
<annevk>
I had this idea of making static copies once people request a particular diff and then making some lookup table for redirects to those static copies
11:57
<Hixie>
that'd be neat
11:57
<annevk>
I wasn't actually planning on ever writing it :/
11:57
<Hixie>
i don't really understand why the usage is so spiky
11:57
<Hixie>
is google crawling it or something?
11:58
<annevk>
could be, yes
11:58
<annevk>
well, we have '<meta name="robots" content="index, nofollow">'
11:59
<annevk>
there's not an easy way to disallow indexing URIs with ? characters, is there?
11:59
<annevk>
(there's of course a lot of direct links from twitter)
11:59
<Hixie>
robots.txt Disallow: / or something
12:00
<Hixie>
i dunno
12:00
<annevk>
I guess I could prevent indexing /tools/ yes
12:00
<annevk>
it doesn't really matter anyway to bots
12:00
<virtuelv>
hm, the science vs. engineering discussion in the backlog is interesting
12:01
<annevk>
http://html5.org/robots.txt
12:19
<Hixie>
nn
12:19
<Lachy>
hmm, weird. I just got an auto-responder mail from the W3C mailing list system in response to my latest mail telling me how to subscribe to public-html, agree to the patent policy, etc.
12:47
<Philip`>
annevk: You could clone the svn.whatwg.org repository onto html5.org, and then you can just do local diffs and hammer your own server instead of someone else's
12:50
<annevk>
Philip`, neh
12:58
<Philip`>
There is clearly an unfulfilled desire for a way to mark up layout tables
12:59
<Philip`>
About 0.2% of pages on dmoz.org have <table summary="some string containing the substring 'layout'">
12:59
<Philip`>
Uh, 0.3%
13:00
<Philip`>
Some people are willing to put a lot of effort into that markup - "Layout table: Main table. The first row contains a USDAFS link and a service wide drop-down navigation. The second row and third rows contains the forest name and search engine. Below this are two cells. The left cell contains the site navigation. The right cell contains the content of the page."
13:01
<annevk>
-_-
13:02
<Philip`>
(e.g. http://www.fs.fed.us/wcnf/unit/ogden/)
13:05
<Philip`>
http://www.google.com/search?q=rfc2328 - "www.ietf.org/rfc/rfc2328.txt ... by O Version" - good to see the author name heuristics working well
13:05
<Lachy>
I wonder if authors that use summary="Layout table" (or similar) actually think of the summary as more like a comment, rather than anything users actually see
13:06
<Philip`>
summary="Logo and Pictures layout. If this summary can be approved please email webmaster⊙sc"
13:06
<wilhelm>
Interesting. How many use <table summary> with any content?
13:07
<Philip`>
wilhelm: About 2.5% of the pages have <table summary>
13:08
<Philip`>
wilhelm: About 2.1% have <table summary="not an empty string">
13:08
<Philip`>
wilhelm: (and about 0.6% have <table summary="">)
13:09
<Philip`>
wilhelm: (obviously with some overlap between those sets of pages)
13:09
<wilhelm>
Right. Thanks. (c:
13:12
Philip`
proposes paving the cowpath by requiring authors to use summary="layout table" (case-insensitively) on layout tables, and suggesting that UAs use that to decide to render it as a layout table rather than a data table
13:30
Lachy
realises that the element categories have changed significantly since I last wrote that section in the html5 authoring guide
13:56
<Lachy>
I think I need to make some sort of diagram that illustrates the relationship between the various element categories, especially: Embedded Content --> Phrasing Content --> Flow Content
13:59
<Philip`>
Hixie: You have a broken link to #durationUpdate - should that be #durationChange?
14:00
<Philip`>
Hixie: Also you have a broken link to #repetition
14:05
<Lachy>
jgraham, annevk or someone else who knows python, where can I find the API reference for the simpletree that html5lib returns? Does it implement some of the DOM API or something entirely different?
14:06
<Lachy>
I need to write a script that processes the spec and extracts all the data about elements and outputs it to a nice table
14:06
<Philip`>
Lachy: import html5lib; help(html5lib.treebuilders.simpletree)
14:07
<hsivonen>
when one writes Python code with html5lib and lxml, would the same app code work with a pure-Python ElementTree impl?
14:09
<Philip`>
Is http://codespeak.net/lxml/compatibility.html relevant?
14:09
<annevk>
Lachy, simpletree is probably best learned by viewing source :)
14:09
<annevk>
s/viewing/view/
14:11
<Lachy>
annevk, what are the advantages of using simpletree over minidom or something else?
14:12
<annevk>
simpletree has some custom functions we wrote, such as hilite, but I don't think it's much more useful than the other tree implementations, and likely slowe
14:12
<annevk>
r
14:13
<Lachy>
ok, I'll use minidom, since that'll have an API I'm somewhat familiar with
14:13
<Philip`>
lxml is what all the cool people use
14:14
<Lachy>
ok, I'll take a look at lxml
14:22
<Lachy>
OMG, what is it that makes people think excessive CC'ing of irrelevant people and lists is a good thing to do? http://lists.w3.org/Archives/Public/public-html/2008Sep/0009.html
14:23
<Lachy>
CC'ing the chairs isn't necessary, since they're already on the list, the wai-* lists are irrelevant to a discussion about editors, and bringing TimBL at this stage seems way over the top
14:25
<annevk>
yeah, weird
14:28
<Lachy>
it's also interesting that all the responses have been commenting on the requirements to be an editor, rather than anyone stepping up and saying they'd be willing
14:29
<hsivonen>
http://code.google.com/p/jython-elementtree/source/browse/trunk/elementtree/ElementTree.py#898
14:29
<hsivonen>
yet another place where the empty element list needs amending
14:29
<Philip`>
Hmm, I can make the spec-splitter 15 times faster by using lxml's HTML input/output instead of html5lib - does anyone mind if I use that (and get slightly different output)?
14:30
<Philip`>
hsivonen: http://google.com/codesearch?q=area+base+basefont+br+col - there's a load more
14:30
<annevk>
I don't
14:32
hsivonen
wonders what Fredrik Lundh's business model is
14:36
<Lachy>
how do I check what versions of libxml2 and libxslt I have on my system? I want to find out if I need to upgrade them for use with lxml
14:38
<Philip`>
grep LIBXML_DOTTED_VERSION /usr/include/libxml2/libxml/xmlversion.h
14:38
<Philip`>
perhaps
14:39
<Philip`>
and grep LIBXSLT_DOTTED_VERSION /usr/include/libxslt/xsltconfig.h
14:40
<Lachy>
it returned: define LIBXML_DOTTED_VERSION "2.6.16"
14:40
<Lachy>
and: #define LIBXSLT_DOTTED_VERSION "1.1.12"
14:40
<Lachy>
ok, I need to upgrade those
14:53
Philip`
finds it hard to remember what it was like to have to manually install and upgrde software, rather than typing a single command and having it all work automatically for pretty much any software package
14:58
<hsivonen>
Philip`: what do you do with software that doesn't have aptable packages?
14:59
<Lachy>
well, I just downloaded and compiled the source for libxml2. Typing ./configure; make; sudo make install; wasn't too hard
14:59
<hsivonen>
Lachy: now, try to remove it fully
14:59
<Lachy>
though it seems to have installed it in a different directory from where the old version was
15:00
<Lachy>
hsivonen, no idea how :-)
15:00
<Philip`>
hsivonen: I care more about things without emergeable packages, but in practice those things pretty much never exist :-)
15:01
<hsivonen>
can html5lib be emerged already? what about Java stuff?
15:01
<Lachy>
I wish Apple provided an easy way to upgrade things like this on Mac
15:01
<hsivonen>
Lachy: sudo port install foo
15:02
<Lachy>
hsivonen, yeah, but that's not maintained by Apple, and how up to date are macports?
15:02
<hsivonen>
dunno about up-to-datedness
15:04
<Philip`>
hsivonen: Those things are much easier than C libraries, since I can just drop the directory/JAR in the right place
15:05
Philip`
was surprised recently to discover Gentoo had the necessary libraries to compile and run a 16-year-old SunOS program
15:06
<Lachy>
$ port installed; tells me I have libxml2 @2.6.32_0 and libxslt @1.1.23_0 already
15:06
<Lachy>
they're recent enough
15:08
<Lachy>
oh, make uninstall; uninstalled everything I previously installed. That was easy
15:08
<Lachy>
I'll just stick with the macport stuff
15:39
<zcorpan>
wonder if i should send comments on the xhtml media types note
15:41
<Philip`>
I imagine your comments would be useful, so that sounds potentially worthwhile
15:42
<zcorpan>
at least it'd be pretty fun
15:43
<annevk>
hah
16:08
<annevk>
whoa, whatwg.org is slow
16:09
<wilhelm>
Indeed. I just got a 500 from whatwg.org too.
16:36
Philip`
wonders if anyone really uses the Accept header, other than as a fragile politically-correct UA-sniffing method to send text/html to IE
16:39
<hsivonen>
Philip`: there could be one or two servers still running legacy code that negotiates PNG vs. GIF
16:39
<hsivonen>
also, I wouldn't be too surprised to find someone negotiating Word vs. PDF
16:40
<wilhelm>
It is used on some mobile sites to determine whether to send WML or HTML.
16:42
<wilhelm>
Incorrectly, usually. They often just sniff for WML, and serve WML if supported. That has caused trouble for Opera more than once.
16:44
<zcorpan>
hsivonen: negotiating png vs gif doesn't have to be legacy code if one still cares about ie6
16:46
<hsivonen>
zcorpan: IE6 claims to Accept image/png, doesn't it?
16:47
<zcorpan>
hsivonen: mine doesn't afaik
16:47
<hsivonen>
ooh. interesting
16:48
<annevk>
I think WebKit and IE do */* + whatever plugins add
16:50
<Lachy>
zcorpan, is there a new version of xhtml-media-types being written?
16:50
<zcorpan>
Lachy: yeah
16:50
<Lachy>
link?
16:50
<zcorpan>
Lachy: it updates xhtml 1.0 appendix c too
16:50
<zcorpan>
http://www.w3.org/MarkUp/2008/ED-xhtmlmime-20080827/
16:50
<zcorpan>
but now it's appendix a
16:52
<Lachy>
LOL. They've got conformance requirements in the abstract :-)
16:52
<zcorpan>
yeah the whole thing is a great laugh
16:53
<annevk>
haha
16:53
<annevk>
btw, Google Chrome: http://blogoscoped.com/archive/2008-09-01-n47.html
16:58
zcorpan
wonders why to not be honest and call it "porn mode"
17:03
<Philip`_>
krijnh: I think your clock is off by five minutes
17:03
<Lachy>
hah, they also seem to indicate that UAs process XML documents depending on which XML MIME type was used instead of just the xmlns
17:06
<Lachy>
"Some HTML user agents render XML processing instructions" - they don't specify which ones. AFAIK, even NN4 didn't render them
17:08
<Lachy>
and they're still recommending the space in <br />
17:08
<annevk>
if the Google thing is a Hoax they did quite a good job
17:10
<Philip`>
It'd be nice if they gave specific examples of UAs where the compatibility advice is relevant; other there's a danger of falling into 'we do it this way because this is the way we've always done it'
17:11
<annevk>
also, http://www.google.com/chrome has a different 404 from http://www.google.com/chroms
17:12
<annevk>
Philip`, I don't think they care much for UAs
17:12
<gsnedders>
University admissions is annoying.
17:13
<zcorpan>
Lachy: in my xhtml mobile study, some rendered the xml decl iirc
17:13
<Lachy>
ok
17:14
<zcorpan>
annevk: catering to UAs is the whole point of the Note
17:14
<Lachy>
guideline #11 and #13 are giving advice optimised for use as text/html, which is incompatible with xhtml
17:15
<Lachy>
i.e. relying on the DOM returning uppercase tagNames and depending on implied elements like tbody in CSS
17:16
<annevk>
zcorpan, that's orthogonal :)
17:17
<Philip`>
"Wouldn't it be great, then, to start from scratch and design something based on the needs of today's web applications and today's users?" - maybe it would, but the list of features in that blog post sounds like pretty much exactly what every other browser already has or is working on
17:17
<hsivonen>
so browsers have gotten so complex that it makes sense design a product around the assumption that browser engines have bugs including memory leaks
17:18
<Philip`>
"We're applying the same kind of process isolation you find in modern operating system" - you mean like how Windows and Linux have all their drivers mushed into a single kernel address space, because microkernels which split every task into a separate process have failed?
17:22
<Lachy>
I like the idea of Porn mode. I maintain a separate clean profile in my browser, which I clear after every use, for that :-)
17:23
<Philip`>
annevk: It would be quite an elaborate hoax since they even got Google to register memoryhog.net two weeks ago to put in an example :-)
17:23
<Philip`>
Lachy: To be extra careful you could use an entirely separate browser, like Lynx
17:24
<annevk>
Philip`, how's that related? (and how did you figure it out)
17:25
<annevk>
(well, I can see how it's sort of related)
17:25
<Philip`>
"If there's a crazy memory leak it won't affect you for that long because you'll probably close the tab at some point and get that memory back." - i.e. "if your browser seems to be going really slowly, you'll have to randomly close a load of pages until you find it's sped up again"
17:25
<Philip`>
annevk: http://blogoscoped.com/google-chrome/6 in the bottom-right refers to memoryhog.net
17:26
<Lachy>
Philip`, of course, I use Lynx for ordinary browsing. I meant I use a separate Lynx profile
17:27
<Philip`>
The process isolation thing doesn't really help at all when you've got some big complex application like Gmail in a single tab and keep it open for a week, which I would guess is where memory leaks are most likely to occur
17:27
<Lachy>
I wonder what appropriate alternate text would be for that. Since it's an image inside a link, the HTML5 spec says to use text that describes the destination of the link. But the image is also one page of a comic strip.
17:28
<Lachy>
but it's making each one a link to the next in sequence
17:28
<hsivonen>
if the entire process gets trashed often, I wonder if one could just make a malloc that bumps a pointer and a no-op free()
17:28
<annevk>
Philip`, interesting
17:29
<annevk>
various googlechrome domains were registered "by proxy" on August 3
17:29
<hsivonen>
does page 8 imply something about Flash?
17:33
<Philip`>
If its engine is based on WebKit, how come "When we started we were passing 23% of WebKit's layout tests" (p11)?
17:36
<annevk>
because the "Denmark V8 Team" made their own JavaScript engine?
17:38
<Philip`>
Maybe they forked WebKit and started hacking on it with no real idea what they doing and broke everything and then someone said "hey guys, we broke three quarters of all these tests, we probably shouldn't have done that" and so they crawled back up to 99%
17:39
<Philip`>
(There are probably more charitable explanations :-) )
17:39
<virtuelv>
where is that 23% quote from?
17:40
<Philip`>
Compiling JS to machine code would be kind of novel if Firefox hadn't done that weeks ago
17:41
<Philip`>
virtuelv: http://blogoscoped.com/google-chrome/11
17:42
<virtuelv>
blogoscoped is so totally hammered now
17:42
<Philip`>
Wow, an address bar that searches more than just the URL, like page titles and stuff! I bet no other browser has thought of that and implemented it and shipped it or at least included it in the latest public beta
17:43
<virtuelv>
shipped, actually
17:43
<Philip`>
IE only has it in the beta
17:43
<gsnedders>
OpenDNS's shortcuts work fine :P
17:43
<annevk>
http://thetruthaboutmozilla.wordpress.com/2008/02/25/the-google-browser/ has some interesting analysis
17:45
<Philip`>
virtuelv: There's an easy solution to that hammering: just open all 38 pages in background tabs, and come back in a while when they've all loaded
17:52
<virtuelv>
Philip`: yeah, or I can wait until someone has done that for me, and can just provide me with zips of the images
17:52
<virtuelv>
or I can wait till the server cools off a bit
17:53
<Philip`>
Ooh, I might have found something that isn't already in other browsers: a newly opened tab automatically shows pages you've visited most often, unlike Opera which is pretty much the same but requires you to click a bit to set the pages to be displayed, and unlike IE8 which shows recently closed tabs and some other stuff
17:54
Philip`
wishes Scott McCloud was better at drawing checked shirts
17:59
<Philip`>
Hmm, I can't find anything else that's novel
17:59
<Philip`>
Did I just miss all the exciting parts?
18:01
<annevk>
putting tab buttons on top?
18:01
<annevk>
I can see why Google has been so active on ES4 now
18:01
<virtuelv>
annevk: I fail to see the novelty of that
18:01
<virtuelv>
<nudge>
18:01
<Philip`>
Opera already has the tab buttons on top of the address bar
18:02
<Philip`>
and IE already does something crazy with the position of the menu bar
18:02
<annevk>
I thought they would put them on top of everything
18:02
<virtuelv>
Philip`: you're refering to the fact that application menus are below the address bar in IE?
18:03
<Philip`>
virtuelv: I think so, though I don't remember exactly what it does
18:03
<annevk>
ok
18:03
<hsivonen>
so when are we going to see benchmarks of V8 vs. TraceMonkey?
18:04
<hsivonen>
for reference, it would be cool to see Rhino generating Java bytecode and HotSpot JITting that as part of a pure-JS benchmark
18:05
<Philip`>
annevk: I'd bet they're not going to manage to put the tab buttons sticking out the top edge of the window in a way that doesn't totally break my KDE theme, but maybe they're not concerned about that :-)
18:05
<Dashiva>
Maybe the tabs will stick out above your screen
18:05
<Dashiva>
So you can physically select them!
18:05
<Philip`>
It'd be fun learning how to move and resize a window that has tab buttons sticking out of it
18:06
<Philip`>
I suppose the V8 "hidden class" thing might be interesting, particularly in comparison to TraceMonkey's tracing optimisations that are trying to solve a similar problem
18:07
<Dashiva>
Aha!
18:07
<Philip`>
(i.e. the variables-usually-stay-the-same-type-but-not-always-so-you-have-to-be-very-careful-before-optimising problem)
18:07
<Dashiva>
This time I wasn't tricked by the month change in the public-html archives
18:08
<Philip`>
Dashiva: Because you bookmarked the /latest URL instead?
18:08
<Philip`>
(Oh, actually, that's probably not really what the hidden class thing is about at all)
18:09
<hsivonen>
now blogoscoped died totally
18:09
<annevk>
I guess nobody made a backup?
18:09
<annevk>
oh well, doesn't matter
18:09
<annevk>
time for food anyways
18:10
<Philip`>
Try http://blogoscoped.com.nyud.net/google-chrome/ ?
18:10
<Philip`>
(That appears to work fine for me)
18:11
<Dashiva>
Philip`: No, because I realized what date it was :)
18:11
<hsivonen>
Philip`: thanks
18:13
<annevk>
lots of UI stuff copied from Opera, indeed
18:13
hsivonen
wonders if Google has tried to buy Opera at any point
18:14
<Philip`>
annevk: Lots copied from IE too, like separate processes per tab, and lists of popular related sites
18:15
<Philip`>
and the rest is copied from Firefox and Safari
18:17
<Philip`>
(Well, not necessarily copied, since they've all been working on these things in parallel over the past couple of years)
18:20
<Philip`>
Also there's the question of how it can be a profitable product, because it's not like they can get a hundred-million-dollar search-box contract with themselves and make money off the deal
18:20
<zcorpan>
http://lists.w3.org/Archives/Public/public-xhtml2/2008Sep/0000.html
18:22
<zcorpan>
Philip`: maybe if people wouldn't use other browsers they wouldn't have to pay the vendors for their search boxes
18:22
<annevk>
"This abstract sucks." so much for zcorpan being the good cop
18:22
<annevk>
:p
18:23
<Philip`>
zcorpan: That sounds a slightly convoluted way of considering their browser to be profitable, but I suppose it makes sense :-)
18:23
<hsivonen>
annevk: the XHTML2 WG exposes even zcorpan's good cop bounds :-)
18:23
<zcorpan>
annevk: i'm the good cop?
18:24
<hsivonen>
zcorpan: annevk is the bad cop. :-)
18:25
<zcorpan>
ok, sorry, i should have let you drop that line in a reply
18:26
<zcorpan>
gotta go now
18:30
<takkaria>
mm, I remember when NS4 was still something people worried about
18:34
<Philip`>
takkaria: That was a long time ago
18:35
<Philip`>
Did you have running water back then?
18:35
<takkaria>
I do believe so
18:35
<gsnedders>
zcorpan (if you read this): "Comments on this document may be sent to www-html-editor⊙wo (archive). Public discussion on this document may take place on the mailing list www-html⊙wo (archive)."
18:35
<gsnedders>
:P
18:36
<Philip`>
Presumably that's an RFC 2119 "MAY"
18:44
<hsivonen>
zcorpan's comments are spot-on.
18:44
<hsivonen>
I wish the document doesn't get published in that state
18:45
<Philip`>
It'd be pretty surprising if it did get published in that state, what with all the "@@@@add example@@@@"
18:46
<annevk>
if it gets published, we can just make a blog post
18:46
<Dashiva>
Philip`: It's for extensibility
18:47
<Philip`>
Blog posts don't look nearly as official as W3C Notes
18:47
<hsivonen>
Philip`: some blog posts get more implementor support, though
18:48
<hsivonen>
like feed autodiscovery
18:48
<gsnedders>
hsivonen: No, feed autodiscovery is done in a way different to any blog post or draft spec
18:49
<hsivonen>
gsnedders: do you mean the HTML5 spec is wrong there?
18:49
<gsnedders>
hsivonen: Next to nothing supports @rel=feed
18:50
<Philip`>
hsivonen: This is more about authors than implementors
18:50
<hsivonen>
Philip`: indeed
18:50
<Philip`>
and I would guess authors are more likely than implementors to consider the W3C authoritative
18:51
<Philip`>
(even if they then choose to ignore that authority)
18:59
<krijnh>
Philip`: I think so too :)
19:00
<Philip`>
One advantage of using irssi+screen+ssh is that I have two independent clocks on my screen, so I can tell if one of them has gone wrong
19:02
<hsivonen>
Philip`: shouldn't one have three clocks to tell which one is wrong?
19:05
<Philip`>
hsivonen: No - I just need the two clocks so I detect the existence of a problem, and then I'll check that ntp is still running on both machines and restart it when necessary :-)
19:17
<Philip`>
hsivonen: When I use the text field entry in validator.nu, then click "validate", the resulting page has "address" selected instead of "text field", so if I click "validate" again then it fails because it was given an empty address instead of resubmitting the text
19:19
<hsivonen>
Philip`: yeah. that sucks pretty badly
19:19
<hsivonen>
Philip`: I wanted to find a purely client-side solution
19:19
<hsivonen>
but I haven't been able to find one.
19:20
<hsivonen>
so I guess I'll just bite the bullet and do something on the server side
19:21
<Philip`>
Okay - if it's a known problem, then that's fine, and I don't have a burning desire for it to be fixed as soon as possible
19:25
<hsivonen>
it annoys me, too, and I believe it annoys other people as well
19:28
<zcorpan>
hsivonen: a way to improve it and still keep it purely client-side would be to show the textarea if source is shown
19:28
<zcorpan>
hsivonen: that's actually pretty much what validator.w3.org does
19:28
<hsivonen>
zcorpan: wouldn't that be bad if the user enables showing source for regular GET urls?
19:29
<zcorpan>
hsivonen: why would it be bad?
19:29
<hsivonen>
zcorpan: the UI wouldn't feel stable. it would be the reverse of the current usability bug
19:30
<hsivonen>
zcorpan: I don't see that behavior on validator.w3.org
19:30
<zcorpan>
hsivonen: perhaps it was the experimental version
19:30
<zcorpan>
hsivonen: you could still revalidate and having the textarea is nice for tweaking and testing
19:32
<zcorpan>
hsivonen: hmm i probably remembered wrong about v.w.o
19:37
<gsnedders>
Time to update my about page with something a bit saner.
19:37
<hsivonen>
hmm. my abstraction layers are so unleaky, that the code that has the opportunity to write stuff in the response doesn't even know the input came from textarea
19:44
<hsivonen>
hmm. I guess I should use setAttribute on ServletRequest to forward this datum
20:08
<hsivonen>
hmm. if IE8 supports hashchange, it might become the first feature of V.nu that is IE-enhanced
20:16
<gsnedders>
Anyone with access to the OED around and able to look anything up for me?
20:17
Philip`
has access to the online one
20:17
tndH
raises hand too
20:17
<gsnedders>
Does it make any preference between the capitalization of mummy v. Mummy?
20:18
<Philip`>
For any particular meaning of the word?
20:18
<gsnedders>
One's mother
20:19
<Philip`>
It uses lowercase everywhere, as far as I can see
20:20
<Philip`>
For "mum" it says "Forms: freq. with capital initial.", but it doesn't say that for "mummy"
20:20
<gsnedders>
k.
20:21
<gsnedders>
"This led to the interesting statement that I made while a toddler, <q>I have three parents — a mummy, a daddy, and a Fiona.</q>."
20:22
Philip`
would use a capital letter when using the word as a name ("I like Mummy") and not when using it as a noun ("I like my mummy")
20:23
<gsnedders>
I on the whole would always use lowercase
20:23
<gsnedders>
Actually, the OED may state that proper nouns should start with a capital somewhere else
20:23
takkaria
is happy he's in hir new flat, there's a church over the road and they practice bellringing on monday evenings :)
20:24
<gsnedders>
takkaria: You'll get annoyed with it eventually :)
20:24
<takkaria>
the eventual solution will just be to play loud music over it, I think
20:24
<gsnedders>
Yeah, that's what I do with bagpipes around here
20:26
<takkaria>
I'm somewhat tempted to wander over and ask how I can get involved
20:26
<takkaria>
I hear that church bellringers quite often don't care about your religion
20:26
<gsnedders>
takkaria: It's hard :P
20:26
Philip`
used to share an office with someone who rang bells
20:26
<takkaria>
gsnedders: as in physically strenuous?
20:27
<Philip`>
and my supervisor does bellringing too
20:27
<gsnedders>
Philip`: In your office?
20:27
<gsnedders>
takkaria: No, in terms of timing
20:27
<Philip`>
(I'm fairly sure they're both non-religious)
20:27
<gsnedders>
takkaria: Because of the delay between pulling the string and the bell ringing
20:27
<Philip`>
gsnedders: No - sadly I've never worked in an office that contains church bells
20:27
<takkaria>
mm
20:29
<gsnedders>
http://digg.com/business_finance/With_Gustov_Strengthing_You_Need_to_Fill_up_NOW?t=18346414#c18346414
20:29
<gsnedders>
How is that not -40?
20:29
<Philip`>
gsnedders: Can't you just ignore the ringing and concentrate on matching your timing with the movements of everyone else?
20:29
<gsnedders>
Philip`: That's the easiest way to do it, I expect
20:29
<gsnedders>
Philip`: But still fairly hard
20:30
<Philip`>
It'd be pretty easy to automate
20:31
<Philip`>
You just need a heavy box and a motor and a pulley, and you could make a perfect bellringing machine
20:31
<gsnedders>
Philip`: I have this slight thought that it has been done before
20:31
<Philip`>
It's not like it's a form of music that requires artistic creativity - you just pull the rope at the point where the little book of patterns says you should
20:31
<takkaria>
Philip`: that also destroys a lot of the fun, so I hear :)
20:33
<gsnedders>
Philip`: You can play any music as the little book of patterns says you should
20:34
<hsivonen>
how does the HTML4+RDFa thing work in terms of W3C WG charters?
20:37
<Philip`>
gsnedders: Normally the written form of the music misses out lots of subtle details of timing and volume and whatever else music has, so you can't just unthinkingly play the notes it says
20:37
<Philip`>
whereas I can't imagine there being much subtlety in bellringing, because all you can do is yank the rope
20:49
<hdh>
the Google Chrome paper comic is cc-by-nc-nd, very thoughtful
20:49
<hsivonen>
textarea annoyingness fixed with HTML
20:49
<hsivonen>
it can still be pretty annoying with XML
20:54
<gsnedders>
Describe me in three words.
20:54
<Philip`>
gsnedders: When something can get 555 Diggs despite not even being able to spell "Gustav" right, I wouldn't trust the ratings much :-p
20:57
<gsnedders>
Philip`: P
20:57
<gsnedders>
* :P
20:58
<Dashiva>
It might be a pun, 'gust of (wind)'
21:00
Philip`
wonders how long it'll be until Hixie is accused of being in some Chrome-related conspiracy
21:00
<gsnedders>
Hixie: You made that edit yesterday just to please the Chrome developers! You don't care about the future of the web!
21:01
<Dashiva>
I bet people have been accusing him off-list already
21:01
<Dashiva>
But will we get people saying "Chrome is anti-accessibility"?
21:02
<gsnedders>
Dashiva: Well, duh, Hixie works at the same company, so obviously it is!
21:21
<hsivonen>
Philip`: re: http://bugzilla.validator.nu/show_bug.cgi?id=294 do I need to differentiate URL attributes
21:21
<hsivonen>
or just say "unescaped ampersand"?
21:24
<zcorpan>
hsivonen: unescaped ampersand or typoed entity
21:24
<zcorpan>
hsivonen: bonus points if you can figure out which entity, if any, the author intended ;)
21:25
<zcorpan>
e.g. &nbspM is clearly intended to be &nbsp;
21:25
<hsivonen>
zcorpan: maybe later for the quessing :-)
21:26
<zcorpan>
http://www.google.com/search?q=%26nbspm
21:27
<Philip`>
hsivonen: It'd seem nicer if you could differentiate between the very common <a href="foo?bar&baz"> and the less common <img alt="Fish&Chips"> or <span>Fish&Chips</span>, since the advice given to authors would be different in those cases
21:28
<zcorpan>
Philip`: isn't it "escape & as &amp;" in both of those?
21:28
<Philip`>
and also it'd be nicer if those could be differentiated from &bogus;, since you shouldn't tell people to escape & as &amp; in that case
21:28
<hsivonen>
http://code.google.com/p/chrome/ is Forbidden
21:28
<hsivonen>
http://code.google.com/p/google-chrome/ is Not Found
21:29
<Philip`>
zcorpan: Hmm, true; but maybe the explanation of the advice would be different
21:29
<zcorpan>
Philip`: why?
21:32
<Philip`>
zcorpan: Because specific advice ("When you are writing a URL which contains a &, you have to write it as &amp;", "When you want a '&' character to appear on the page, you have to write it as &amp;") seems friendly and easier to understand than generic advice
21:36
jgraham
belatedly notes that he also works with someone who is into bellringing
21:53
<BenMillard>
Lachy & jgraham, thanks for your review of the tables. I've replied with updates.
21:58
<Lachy>
BenMillard, looks good
22:00
<gsnedders>
BenMillard: Did you book the hotel, BTW?
22:03
<BenMillard>
gsnedders, not yet, sorry. Been swamped with tables stuff, my collection midpoint and a usability audit which has just come my way.
22:03
<BenMillard>
I send an e-mail asking about availability, though
22:03
<BenMillard>
*sent
22:03
<gsnedders>
BenMillard: Do you mind if I just give you the amount in cash there?
22:04
<BenMillard>
gsnedders, that's fine by me
22:04
<BenMillard>
Lachy, I've just swapped 3 & 4 with 5 & 6 so they have a slightly more logical progression.
22:06
<hsivonen>
BenMillard: I'll review in the morning
22:07
<BenMillard>
hsivonen, thanks. :)
22:14
<Lachy>
BenMillard, you also have to change the links in the article
22:15
<BenMillard>
Lachy, I had but SmartFTP has decided against uploading it for the past several minutes...
22:16
<BenMillard>
Lachy, should be correct now.
22:16
<Lachy>
yep, that's better
22:17
<hsivonen>
BenMillard: actually, reviewing now
22:25
<BenMillard>
hsivonen, I'm making some editorial tweaks to the entry so it reads a bit better. Also, I need to do a recount of cells, bytes and so forth.
22:25
<BenMillard>
the redesigned tables should be stable, unless you find errors :)
22:30
<zcorpan>
hsivonen: nice! one thing though, the select says "address" but the textarea is shown
22:30
<zcorpan>
hsivonen: solved by modeSelect.value = urlInput.className
22:31
<BenMillard>
zcorpan, interested in reviewing my attempts to simplify a headers+id example? (It's what lachy and hsivonen have been reviewing.)
22:32
<hsivonen>
zcorpan: thanks. I'll fix in the morning
22:33
<zcorpan>
BenMillard: sure. pointer?
22:33
<hsivonen>
BenMillard: good stuff. thanks for examining this
22:33
<hsivonen>
(email sent)
22:33
<hsivonen>
nn
22:34
<zcorpan>
nn hsivonen
22:35
<BenMillard>
zcorpan, I'm keeping it off-the-radar until I'm sure it's of good quality. Am forwarding the e-mail to you now (which includes the links).
22:35
<zcorpan>
BenMillard: k
22:36
<zcorpan>
BenMillard: you could have just sent it to cabal⊙wo :P
22:37
jgraham
likes that BenMillard considers public IRC to be "off the radar"
22:37
<zcorpan>
oh wait this channel is logged?
22:37
<zcorpan>
crap
22:37
<Philip`>
[off] the radar?
22:38
<BenMillard>
jgraham, keeping the links private to avoid premature public review is all I want. :)
22:38
<BenMillard>
zcorpan, d'oh, I'll remember that text time! Forwarded.
22:38
<jgraham>
BenMillard: Only teasing :)
22:40
<BenMillard>
hsivonen makes an interesting observation: "Does it make any sense to group by "budgeted" major and date minor to put all three "budgeted" columns side-by-side, etc.?"
22:40
<BenMillard>
so the dates would be repeated instead of the aspects
22:41
<zcorpan>
BenMillard: ah my hotmail address. never check that these days
22:41
<BenMillard>
zcorpan, that's the only one I have for you...
22:42
<zcorpan>
BenMillard: no need to resend but simonp⊙oc or zcorpan⊙gc has a higher chance of me seeing the email :)
22:42
<BenMillard>
zcorpan, oh actually I'm lying! I do have an @opera for you, sorry.
22:42
<Lachy>
zcorpan, does cabal⊙wo actually work?
22:42
<zcorpan>
Lachy: dunno
22:42
<Lachy>
maybe we should set it up :-)
22:42
<jgraham>
Lachy: I guess Hixie might get it
22:42
<zcorpan>
send an email there and see what happens
22:44
<jgraham>
BenMillard: I think the answer is "without knowing the purpose of the table it's hard to say"
22:44
<Philip`>
It's not much of a cabal if Hixie is the only person in it
22:44
<jgraham>
Philip`: Best kind of cabal
22:44
<jgraham>
Most exclusive
22:44
<zcorpan>
it's Hixie and his cats
22:45
<jgraham>
Maybe he could train the cats to edit the spec
22:45
<Lachy>
Yep, Hixie, Pillar and Hedral are the founding members
22:45
Lachy
hopes he remembed the cat's names correctly
22:45
gsnedders
just claims not to have a clue, and gets away with it
22:45
<gsnedders>
Thankfully, they haven't come after me yet
22:46
<BenMillard>
jgraham, yeah. It seems to me that the table is about comparing the Budget against what was Actual and what was Forecast; rather than comparing how each aspect changed over time.
22:46
<BenMillard>
jgraham, having said that, the Budgeted and Forecase values never change within each investment...so maybe it's really about seeing how the Actual changed each week?
22:46
<BenMillard>
*Forecast
22:47
<jgraham>
BenMillard: I strongly suspect this is fake data
22:47
<BenMillard>
jgraham, that's also a possibility, in which case I'll redesign when we are shown the actual source table. :)
22:47
<annevk>
fyi: http://googleblog.blogspot.com/2008/09/fresh-take-on-browser.html
22:47
<Lachy>
it's not very good fake data. It makes analysing it and working out what's really important quite difficult
22:47
<annevk>
(no need to URL guess anymore)
22:48
<Philip`>
Lachy: They seem correct, judging from http://www.flickr.com/photos/carinda/2672675271/in/set-72157606196286925/
22:48
<zcorpan>
interesting, hotmail stripped out <http://...> when forwarding
22:49
<Philip`>
(unless those are totally unrelated cats and it's just a freaky coincidence)
22:49
<BenMillard>
zcorpan, do I need to resend? maybe it thought they were HTML tags :)
22:49
<Lachy>
Philip`, there's no caption on those cats!
22:49
<annevk>
I wonder what license it will be under
22:50
<Lachy>
grr. X-Chat keeps crashing when I accidentally right click :-(
22:51
<Philip`>
Lachy: That's why computers should only have one mouse button
22:51
<jgraham>
annevk: It pretty much has to be LGPL I think
22:52
<Philip`>
Some parts of WebKit are apparently BSD
22:52
<jgraham>
Reaction from the intertubes seems somewaht muted
22:52
<zcorpan>
BenMillard: no need
22:52
<jgraham>
Philip`: they also claim to have used Firefox code
22:52
<roc>
the comic says BSD
22:52
<jgraham>
Which is GPL/LGPL/MPL
22:52
<Lachy>
Philip`, my computer does only have one mouse button!
22:52
<Philip`>
jgraham: Oh, right
22:52
<roc>
perhaps they mean the non-Webkit bits
22:52
<Lachy>
but 2 finger tap behaves as a right click
22:53
<Philip`>
Lachy: Oh, I suppose you'll have to blame God then - if Steve Jobs had designed humans, we'd only need one finger, and all these problems would be avoided
22:54
<Philip`>
jgraham: Combining components from multiple open-source software projects seems a very rare thing
22:54
<Lachy>
hah! :-D
22:54
<Philip`>
Code reuse is usually far too much work compared to just rewriting it yourself
22:55
<Lachy>
roc, on which page does the comic say BSD?
22:59
<Lachy>
wow, blogoscoped.com is very unresponsive right now
22:59
<Lachy>
luckily, I wgeted a copy of the whole comic earlier
22:59
<Lachy>
but I wanted to check if I got them all. Were there only 38 pages?
23:00
<roc>
yes
23:00
<roc>
I can't find the page which said BSD but I definitely saw it
23:01
<zcorpan>
BenMillard: i'll look at this tomorrow, bedtime now
23:01
<jruderman>
in http://blogoscoped.com.nyud.net/google-chrome/37 they implied that it was a BSD-like license
23:02
<jruderman>
jgraham: where did they claim to have used Firefox code?
23:02
<Lachy>
it could also be LGPL or MIT based on that, but I suppose MIT is ruled out because WebKit is BSD/LGPL
23:02
<Lachy>
but then it could be all 3
23:02
<Philip`>
jruderman: http://googleblog.blogspot.com/2008/09/fresh-take-on-browser.html - "We've used components from Apple's WebKit and Mozilla's Firefox, among others"
23:03
<Lachy>
or even Apache2 licence, like google Android
23:03
<BenMillard>
zcorpan, ok thanks
23:05
<jruderman>
Philip`: interesting
23:05
<jruderman>
so they might not have intended for the cartoon to be the first thing we saw ;)
23:05
<roc>
maybe I saw it in Slashdot
23:05
<roc>
in which case, I apologise
23:06
<Philip`>
jruderman: They probably didn't intend to indirectly DDOS the server of the first person who chose to scan and upload the comic :-)
23:07
<jruderman>
lol
23:07
<Lachy>
wow, the idea of a Google browser has been floating around since 2001 http://webword.com/moving/googleclient.html
23:08
<Lachy>
that's even earlier than I thought
23:08
<Philip`>
Has anyone predicted a Yahoo Browser yet?
23:10
<annevk>
prolly
23:10
<annevk>
or rather, toaly
23:15
<gsnedders>
Philip`: I predict Yahoo will launch a browser next year.
23:15
<gsnedders>
Philip`: Certainly.
23:17
<Lachy>
I wonder why Google is restricting Google Chrome to 100 countries?
23:17
<Lachy>
unless they mean 100 UI languages, cause being open source, there's nothing stopping anyone releasing it world wide
23:17
<gsnedders>
Lachy: US export laws
23:18
<annevk>
maybe because Google Search only works for a 100 countries?
23:18
<Lachy>
gsnedders, what do US export laws have to do with anything?
23:18
<gsnedders>
Cuba, Iran, etc. cannot have it sent to from US servers
23:18
<gsnedders>
I can't remember quite what the laws are
23:18
<Philip`>
Lachy: They say "more than 100 countries", which might mean "all the countries in the world"
23:18
<Lachy>
Google have servers in other countries
23:18
<gsnedders>
Lachy: It may be relevant that they have their HQ in Google
23:18
<Philip`>
100 is just a nice round number
23:18
<Lachy>
there are over 200 countries
23:19
<gsnedders>
in Google? in the US.
23:19
<Philip`>
If you get too specific about the number of countries, you'll get into all kinds of political disputes
23:20
<hdh>
maybe 100 launch parties, but it's just a beta
23:21
<annevk>
http://geography.about.com/cs/countries/a/numbercountries.htm says less than 200, fwiw
23:21
annevk
is not sure it's correct
23:21
<roc>
"country" is a fuzzy concept
23:22
<Philip`>
hdh: "just a beta" doesn't mean that much - Gmail is still just a beta
23:23
<Lachy>
LOL, the comic has been taken down due to server load
23:23
<gsnedders>
The web applications wg was always in beta
23:23
<Philip`>
Lachy: The pages other than 1 still work fine
23:24
<annevk>
roc, indeed, http://en.wikipedia.org/wiki/List_of_countries has better information than about.com
23:24
Philip`
predicts that calling Chrome "beta" will not stop lots of people downloading it tomorrow and finding loads of problem and saying it's rubbish and a failure
23:26
<roc>
I think we in New Zealand would classify the Cook Islands, Niue and and Tokelau as independent countries, even though about.com doesn't
23:27
<roc>
they're basically self-governing. NZers would be surprised to be told that we govern them
23:27
<gsnedders>
me predicts loads of people will find loads of problems and say it's rubbish and a failure
23:29
<Philip`>
(In particular, it won't stop me downloading it and finding loads of problems and saying it's rubbish)
23:29
<gsnedders>
Philip`: You normally do, though
23:29
<annevk>
roc, yeah, we'd say the same about Aruba and Netherlands Antilles (although there was some controversy about it recently)
23:30
Philip`
hopes it'll work in Wine
23:30
<roc>
Not to mention my favourite Norwegian possession, Bouvet Island
23:32
<annevk>
haha
23:32
<annevk>
just a plague of ice
23:33
<annevk>
wow, it has a ccTLD
23:33
<annevk>
that's funny
23:33
<roc>
yeah
23:34
<hdh>
gsnedders: can you make "import hotshot" in anolislib optional? python-profiler is not in debian
23:34
<gsnedders>
hdh: I guess
23:38
<gsnedders>
hdh: Remind me tomorrow, if I don't do anything about it by 18:00+01 :P
23:38
<hdh>
ok