I've gotten several e-mails from readers that they haven't been able to leave comments on this blog. I suspect it has something to do with twisty comments, but I just tried them in Firefox 1.0 on Windows XP and they seem to be working fine. In order to help me track down this problem, try posting a comment to this entry and see if it works. Make sure and copy it before you post it, just in case it doesn't work. Clicking on the "Permalink" or title for this post will take you to a backup comment form that seems to work regardless. Thanks for the help!
Update: From the various comments, there doesn't seem to be a common thread. It seems that half the folks that used Firefox + XP it worked for and the other half it didn't. I doubt it's a caching issue, but I have been seeing a lot of the following in my logs:
ERROR 2005-01-22 19:51:01,944 | RequestProcessor:processMapping | Invalid path /comment was requested
Roller recently changed from using /comment to /comments - so I don't know if it's spammers hitting the old URL or what. My guess is yes since it seems to happening in blocks. I'll try to add a preview button tonight so users will get taken to the permalink form for previewing. Either that or I could just change to always using the permalink form. It's up to you guys - let me know what you prefer.
Patrick thinks that Ruby on Rails is all hype.
Now maybe I'm just a bit biased since my framework isn't getting all the slashdotters oohing and awwing over it, but I think Ruby on Rails is way
over hyped. The tutorial here is great and gave me a very good overview
of what it does. At the end of the day, RoR is simply a RESTful CRUD framework.
I'd like to agree with Patrick, because that is my natural tendency when I see a project that everyone praises. But I know better. I think it's better not to speculate on the productivity or usefulness of a framework until you've used it to develop an app.
That's what I did with Spring, WebWork, Tapestry and JSF last year. Now I feel like I know "the truth" and whether one framework is better than the other. The truth is they all have strengths and they all have weaknesses. While one might work well for one project, it might not for the next. I think the best thing is that you don't setup yourself for framework lock-in. If you only know one web framework for Java, you should probably pick up a book and develop an app with another framework - just to see how things are done differently. Now that I've used all of the Big 5 in Java, I don't think it would be that hard to migrate an app from one framework to next.
So what am I trying to say? Don't bash on a framework until you've tried it. And I don't mean toying around with it on a Tuesday night, I mean using it for a real-world project. I'll probably diving in and doing a little Rails development later this year. Why? So I can see if all the hype is accurate. 
