My generated code is less space-efficient than my original hand-hacked version; the game is now a whopping 13K (as opposed to the previous 11K).
ObSegfault: DST Bug causes Widespread Panic. "In this reporter's opinion, what Los Angeles needs is more freaky chicks with big hair and guns, who ride around on motorcycles and dispense vigilante justice."
I'm uncertain as to the value of releasing the source code to and bug list for a work of IF immediately after releasing the work itself. Of course, those who want spoilers at any cost can always disassemble the .z5 file. IF is sort of a special case in programming, and even in game programming, since it's so story-driven and artsy. I don't think I could develop an IF story publicly. I mean, I could do it. Psychologically I would adjust. But it wouldn't feel right, and I don't think it would be as good as it would be if I was able to sit on my vision for the game and not tell anyone about it until I was ready.
That said, I think the basic game structure of Guess the Verb! could have been done a lot better, and that a design session with someone else early on could have made it a much better game. (See upcoming GTV! post-mortem.)
Speaking of which, I really like the developer-written game post-mortems at Gama Sutra, even though I've never played one of the dissected games. I wish that post-mortems could be done for more types of software, but games are 1) relatively unimportant, obviating the need for compulsive litigators to sue because a developer mentioned publicly that a product actually has a defect; 2) a category where, eventually, you can actually claim to be done, rather than just having attained a certain version number.
Back to IF: a whopping *two* bugs were found in the djinn game. I am amazed and flabbergasted, and both bugs have been fixed. It's true that there is always one more bug...
Also, I have coined a phrase: "constructive carping". I'm not sure of the precise definition, but it's sort of the Dan Helfman school of software design.
"[B]oy was that wacky." -- Emily Short
Actually, I can see how this might not work if you were a woman.
Reclufteg Ftalabesp Trastrar Echrort
Bedradric Nfatusorm Rcytchep Achrons
Actual subject lines from actual spam, folks. Of course, it's just the usual make-money-fast crap.
Why wait another SECOND when RIGHT NOW your finite, temporal body could be wracked with MONEY!?*
Thanks, Kris.
I'm keeping track of the titles so that once I have a hundred or so I can cycle them the way I cycle the quotes. So far I only have 21.
The one redeeming feature of the song is that Zeppo sings it at the beginning of the movie and gets it over with, and then at intervals later on the other three brothers perform travesties upon it. Groucho:
Everyone says "I love you"
But just what they say it for I never knew
It's just inviting trouble for the poor sucker who
Says "I love you"
Then the musical phrase that leads into the next stanza sounds like the "Your way, right away" riff in those old (though postdating Horse Feathers) Burger King commercials.
Susan meets all the requirements for me to link to her journal on the navbar, but for some reason I've been resisting it. It used to be because her journal was completely illegible, but now only half of it is completely illegible.
Pictures from Kevin's camera coming soon to a theater near you.
I would just like to point out that in Bakersfield, you do not need an appointment to get your car's oil changed.
Also, it is interesting to note that the only place the word "rhinoceros" appears in that book is in the title. Presumably this is for reasons of historical accuracy.
Type mismatch: Could not cast "Technical Paper" to type "RTOS"
Also on Saturday I articulated my idea for the football mascot of a deconstruction-heavy university: The Fighting Other.
A similar convention is taking place, where many innocent, virginal gawky male anime characters are exposed to girls hitting on them, winking at them, etc., and the gallons of blood rocketing out of their noses are collected and sent to the Red Cross.
I think he misunderstood my usage of the word "convention", but still, what a snappy comeback!
You may have noticed that I am not particularily fond of San Francisco. I've decided that I don't really like L.A. either, so moving back to L.A. is not the answer. What is?
It's so foggy and gloomy tonight... How foggy and gloomy is it? It's so foggy and gloomy that I'm posting deep, searching questions about my life to my weblog.
What the beautiful caching does is it stores the results of previous permission checks so that the next time that same permission is checked, it doesn't have to run the algorithm again. The cost of running the algorithm has been reduced to the cost of a hash table lookup. Anything that invalidates the beautiful cache also invalidates your ACL, so you don't need to worry about invalidation. It is, in a word, beautiful.
Permission checking used to cause over half of the user-visible delay on Tigris sites, just because it was such a common action. The beautiful caching (in association with other types of caching) basically reduces this to zero; as Jody said, "At last, free checking." Unfortunately, I neglected to backport beautiful caching to the 1.0 branch, so JXTA doesn't have it right now. But it probably will soon.
Next time: Clustering, RMI, and You
This is all purely hypothetical. I don't think I want to use the OAL. A copyleft license for music doesn't sound right. Perhaps my long proximity to BSD advocates has affected my judgement.
I really need to update Leonardonics.
Just pointing that out.
Disclaimer: I know nothing about JXTA, except that their site doesn't use my scalability improvements, but I brought this up in a meeting and Dan didn't object.
Fri Apr 27 2001 15:47 When The UNIX Philosophy Goes Too Far: First In A Series:
Sun Apr 29 2001 11:19 Tonight's Episode: Murder At Random: