You know, I've only barely started with WebKit, but I've been so happy with
how easy it is to get it going. To this I compare:
1. mod_python: Requires a threadless Python install. I tried. I really,
really tried. What a nightmare. And once you've got it in... Well, you still
need a framework, unless you've been specially reinforced against suicidal
2. iHTML: A ColdFusion alternative. It took me 3 months, no kidding, to
actually get this thing running. It never had enough proper error logging,
and no arrays, either. As a DSO, it was *very* finicky about running with
Apache. Typical behavior in trying to get it to work? Start Apache, and,
wow, there aren't any httpd processes actually running. And on top of all
that, it's the only piece of software that's ever run one of my Linux boxes
out of file descriptors. And you know how well *nix behaves when it runs out
of file descriptors. Since this product is closed-source, I gave up hope.
Of course, I'll probably complain a lot when I discover Chuck hasn't already
made a WebKit function that'll convert my no-hit default index.html to the
next Mahir "I Kiss You!", but that can wait.