> If I can give you a suggestion, worry about something when you > actually have that problem, not before.
I don't know if I really agree with this. I'd rather head off a problem far in advance of it ever becoming one, which is why I didn't want to doom myself at the start. However, I do agree that it may be silly to worry about a (negligible?) speed improvement over an app that I haven't even started yet. I just wanted to make the right decision from the start so that I have to never look back and would never have to do a complete code rewrite due to the language. And also I agree with your comments about bottlenecks. I think more of a site's performance relies on database optimization more than the language itself. However, I could be wrong. > > I've read a ton of comparisons that compare one framework to another, > > and one language to another. There's so much conflicting advice out > > there that it's hard to know what is best. Did I make the right > > choice choosing Rails for my first web project? I guess we'll see. > > Depends on the project. I guess what's solidifying my choice for Rails is that it was pulled from a far more collaborative site than Django (which was born from a newspaper site). Although I'm sure both of their underlying languages are capable of far more than that, I fear that I'm reduced to using to a framework due to my current level expertise (which is none at the moment). > Welcome. > > ngw Thank you! and thanks to everyone else that's chimed in on this thread. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" 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/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
