It is about a week I'm experimenting with Ruby and RoR.
I know there are no perfect tools and while I really enjoy the RAD part of Ruby *and* RoR and even more I enjoy how Ruby makes programming funnier I know that software maintenance is the real pain.
First short term problem is:
does the RoR framework makes easy to implement ajax as well the corresponding non ajax fallback or should I code twice anyway?
I've the feeling that ajax (or something similar) will be the future (at least somehow I hope so) but not now and not tomorrow. Surely by the time I'll learn RoR reasonably well to consider it an investment, tomorrow will be nearer... but I've bills to pay now and it doesn't make too much sense to learn a tool so fascinating for it's RAD characteristics if you'll be able to make money out of it after 2 years
Long term problem:
I've read about IO problems (and I've a feeling they may be solved in reasonable time) but I've heard about threading problems as well with RoR and as superficial my view may be, those don't seem easy to be solved.
I gave a look to mongrel and to mongrel's author comments and well my feeling was that even an active developer of RoR community has the feeling of "beating a dead horse". Please don't take this as "putting my words in someone else mouth". I'd surely appreciate any correction/clarification by Zed Shaw as it will help me to have a clearer picture.
I'm still looking for an OO programming language that fits into web development and Ruby continue to look as the best choice around. Learning Ruby and keep on writing with php and asp seems a less challenging task than jumping on RoR to develop e-commerce web sites starting from tomorrow.
BTW it seems that RoR is in sid (and maybe etch) that should become stable *shortly* that at least should solve some of the maintenance problems.