Robert Kern <[EMAIL PROTECTED]> wrote: ... > Picking RoR because you want to do the project in Ruby makes sense. > Picking Ruby because it only has one web framework is as silly as picking > one Python web framework at random. Just because RoR is the only Ruby web > framework around doesn't mean it's suitable for every project.
If you claim there's a web project that's unfeasible to do in Ruby, you'd better come up with a strong example. If you're making no such claim, which would be counter to the claims of the Ruby community, then there aren't gonna be any web projects unfeasible with Rails, either. The multiplicity of frameworks in Python obviously makes the situation very different: there might well be projects for which Python's quite suitable IF a fairy godmother pointed you to just the right framework... but lacking a fairy godmother, you're out of luck. To put it another way: one reason I love Python is that I strongly subscribe to the idea that there should preferably be only one obvious way to do something. Unfortunately, this principle is very badly broken by the multiplicity of Python web frameworks. Alex -- http://mail.python.org/mailman/listinfo/python-list
