I have been incredibly frustrated lately, since IIS6 no longer supports logging ASP errors.
A pedant that hangs out in the dark corner-cases of the web.
Saturday, February 26, 2005
XML::DTDParser 1.7 was not parsing all of my attributes correctly, and I noticed that my 'IDREF's were matching as 'ID', leaving an extra token 'REF', and forcing the regex loop to stop.
The module works fine after changing line 18 to:
my $AttType = '(?:CDATA|ID\b|IDREFS?\b|ENTITY|ENTITIES|NMTOKENS?\b|\(.*?\)|NOTATION ?\(.*?\))';
Wednesday, February 16, 2005
So, after winning the browser war, and then completely abandoning any real innovation (like finishing the product so it understands web technologies), and becoming a millstone to all web developers, we're supposed to be impressed at a vague announcement that there will be a new IE this summer?
After months of maintaining that MS is not concerned about Firefox in the face of an incredible adoption rate, they suddenly change course and suggest that there will be a new IE for Windows XP, not just for Longhorn. Apparently, those of us who are aware of what they have done to the web, with their perfunctory support of basic web technology, are supposed to forget just how badly they have hurt the Internet ecology, and like a beaten domestic partner, come back for more?
Don't get me wrong, I like Firefox personally, but I favor no browser software as a developer. I want a fairly even market split because, as we have seen, competition is the only reliable driver of innovation. All I ask is some basic functionality; I'll even wait a reasonable amount of time if there is some indication I can expect improvement.
I really do hope we can expect improvement in IE7, but with the hostility some in the MS community have shown those who ask MS to support the specifications it helped write, I very much doubt any real advances.
IE7 To Do List
- fix the
- fix the
titleattribute is explicitly hidden for some reason)
- fix the
- fix table headers and footers (they don't repeat on each printed page of a table, rows cannot scroll between them)
<optgroup>s work as in MacIE (submenus), and correctly support the
- any XHTML support (using the right MIME type)
- full CSS 2 support (there's a lot to do here: box model, selectors, @import media, dynamic pseudo-classes, min/max-width/height, content, quotes, counters, display)
- full DOM support
window.confirm()should ask a yes-or-no question, not an OK-or-cancel question
- PNG transparency support
- a complete Unicode font, or at least something that supports 0x2000-0x2BFF (symbols)
- a link bar
301 Moved Permanentlyto update bookmarks
205 Reset Contentfor data entry applications
- some kind of RSS support
Thursday, February 10, 2005
An entire generation of programmers has been turned into script kiddies by VisualStudio wizards. Too much detail is hidden from the person writing the code.
For example, try finding any resources on creating a COM control using mingw. Try even finding a book on COM (a technology old enough to have been supplanted by .NET) that isn't merely a tutorial on using VisualStudio. Even O'Reilly & Associates, a company with a celebrated history of documenting open source solutions, is guilty.