Mokka mit Schlag » Software Development

What tools are people using to validate their web pages? In Refactoring HTML so far I’m writing about four, somewhat related tools:

• W3C Validator
• LogValidator
• xmllint
• The button/menu item in your editor that says “Validate this document”

Anything else worthy of mention? In particular, is there anything significantly different enough from these four that it deserves to be called out separately? Or is there anything better that should replace one of these options? (This is a relatively small book, and I am trying very hard not to cover absolutely every possibility and option.) Open source tools are strongly preferred.

It’s a slow Sunday morning so I was going to browse around a new language I’d been hearing rumors of, and maybe send them a little link love if I liked what I saw. However it seems all their tutorials, manuals, white papers, and almost everything else are in PDF. Yuck. Not worth my time.

They’re complaining that they can’t get any thought leaders to pay attention to them. If they insist on publishing on the Web in a format designed for paper books, it’s no wonder no one has noticed them. Write back when you start noticing this little thing called HTML, guys. I’ve got a feeling it’s going to be big one of these days.
(more…)

Rails (and similar frameworks like Seam, Grails, etc.) work by inspecting database schemas and dynamically generating code at runtime. They implicitly assume a SQL database, which isn’t really a good fit for most publishing applications. Sure you can slice and dice documents enough to force them into tables, but it’s a lot like pounding screws into set concrete with hammers.

Many publishing applications, especially generic systems like Wikis, content management systems, and blog engines, would be better served by a native XML database and XQuery; e.g. eXist instead of MySQL. What would a Rails-like system look like in this environment? What would the conventions (instead of configurations) be?
(more…)

Peter Coffee’s list seems about right, though Mac OS X is an OS and a GUI shell, not an app. Throw that away and there’s room for one more.

The only mistake here is the inclusion of Internet Explorer 1.0. That was a horrid product no one used. That should be replaced by Mosaic 1.0, which was far more significant to the development of the Web, and likely had many more users to boot. In fact, few versions of IE had any real significance. Mostly they just copied other browsers and got bundled with Windows. Just maybe you could count IE 5 as a killer app, since that’s the one that introduced XMLHttpRequest, which would become the basis for AJAX and Web 2.0. That’s probably the only significant innovation Microsoft’s ever made in the browser space. But IE 1.0 simply does not belong in this list.

I’m trying to devise a regular expression that will find all or most img tags that don’t have alt attributes. <img[^>]*/> will find all the img elements (or at least most of them). And I can easily find those that do contain an alt attribute. However, I’m stumped when it comes to finding those that do not contain the substring alt. Any ideas?
(more…)

Sleepycat asks some interesting questions about a non-standard persistence API they are developing. By the way, non-standard is good. Ideas like this should be tried out in open source products first before baking them into standards. I applaud Sleepycat for taking this route instead of rushing into the JCP. Indeed standardizing in advance of implementation experience explains a lot of the problems in JEE that APIs like this one are designed to replace. Anyway, on to the questions:
(more…)