The long-awaited (by me) conversion of this blog to Django is underway. After a couple hours’ work I have a full set of models and a functioning admin, and working index and detail views of postings and comments. Searching, posting comments, and tags are the major pieces remaining. Because of my busy schedule I’ll only be able to work on it in fits and starts, but I expect the total labor in the end to be about five hours.
Ironic that I find myself defending PHP at a point when I’m making a huge effort to move most of my web coding to Python, but I keep running across mini-rants along the lines of “PHP sucks because it mixes business logic into your HTML.”
No, it doesn’t.
It makes it possible, sure. But it’s completely avoidable. As The Daily WTF can show you, it’s possible to do screwy things in any language.
Safari and Opera understand CSS files mistakenly sent with a text/plain MIME type. Gecko browsers, on the other hand, do not. Don’t ask how I learned this.
I’ve tiptoed into the Web 2.0 world by adding a couple small Ajax features to the blog.
First, there’s now a “More” link at the top of my Random Bookmarks sidebar which fetches another seven random links from the server and plugs them into the page without reloading.
Second, I added a gratuitous animated roll-unroll toggle to the comment form, and made it closed by default. OK, that’s not Ajax, that’s just fluff.
In recent weeks I’ve been listening to the back-catalog of Ajaxian podcasts while commuting. It’s been great food for thought for me, since I’m one of those people who retreated to the server side years ago to avoid the horror of incompatible, standards-oblivious browsers and crazed animated status bar messages. Things seem to have gotten a lot better, to say the least.
Here are some things that these podcasts have prompted me to think about: