Oh man, I so want this: Time Life Video: The Best of the Muppet Show, 10 DVDs, 30 episodes, for $100 bucks.
The Onion: Mom Finds Out About Blog
"God, my links alone contain unlimited fodder for Mom's neuroses," Widmar said. "She'll have access to not only my life, but the lives of all my friends who have web sites. She'll have the names of all the places in Minneapolis where we hang out, which she can—and will—look up. With the raw materials in my blog, she could actually construct an accurate picture of who I am. This is fucking serious."
Hahahaha.
Also see Wired: ITunes Undermines Social Security
Woo, I'm finally leaving PHP. I have my local mod_python environment set up the way I want it, Cheetah's installed and working, etc. The only thing is that now I have to learn a new environment. The Cheetah documentation isn't good enough, and I'm not sure how I'm supposed to develop with it. I don't think there's a method that will automatically cache a compiled version of a template, for example, so I think I have to do that stuff myself, which is at a lower level than I expected to have to go.
It's not a big deal, and until I'm ready for "production" I can just leave it compiling on the fly for now, but the main issue is that I don't yet have a feeling for how the developers expect you to use Cheetah with mod_python. For instance, most of their documentation is about using Cheetah from the command line (and they have a little bit about using it with Webware too).
The other big problem is that if I get any errors, they go to the Apache error log, even though I have "PythonDebug on" in my httpd.conf, which sucks.
Oh, as for templates, since global variables stay in memory between requests, I could always just leave all my templates sitting around in memory (I don't have that many templates that it would be a problem). However, the fact that everything stays in memory in the first place bothers me a bit. If you ever accidentally assign something to a global variable you might have something big sitting around in memory forever and not realize it. And AFAIK, there's nothing automatic I can use to refresh the global environment, so I may have to write some tools myself to clear things and make sure the GC picks them up.
One more concern is that if mod_python ever starts sucking, or if it just turns out not to be the right solution for me, and I want to switch to Python with FastCGI or SCGI or whatever, I'm slightly worried about how much code I'd have to rewrite. Probably not much... but the point is that I'm still a little concerned about the reliability of mod_python.
Update: Apache error log problem fixed. It seems that PythonDebug must be specified on the directory level. I had it in my httpd.conf, but not in a <Directory> block. I just stuck it in my .htaccess file and it worked fine.
Sunday, November 16, 2003
Permalink
Calif. Supreme Court to take up gay marriage ban
I would argue the point is notdefinitional. While the wordmarriage is su...
Justin: Nov 20, 4:37pm