The differences in speed on webapps are usually entirely due to blocking at the database level. I think a good comparison would be someone driving a 40yr old cadillac and a new sports car in a 5mph school zone lined with cop cars-- it doesn't matter what's under the hood, you're going 5mph.
Pylons and RoR are very similar, and also very not. Pylons is very 'extensible' and allows for more interaction/control of the developer. RoR has a lot of 'magic', which translates to things needing to be done in certain ways. Rails apps are often slow -- not because of Ruby, but because of Rails. I think Pylons might be a bit more similar to Merb. In any event , my suggestion is this: - if your lead guy is a Rails programmer, find a new lead guy - if your lead guy is a Ruby programmer, and he thinks that the app makes sense in Rails or Merb - stick to them and avoid the pitfalls of learning new stuff. - in all other situations, Pylons or Django might just be a great fit! maybe they want to try something new, or they know that its going to be a PITA to get rails to do what you want. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
