Balancing Performance and Convention

markmcb writes "My development team was recently brainstorming over finding a practical solution to the problem that's haunted anyone who's ever used a framework: convention vs. customization. We specifically use Rails, and like most frameworks, it's great for 95% of our situations, but it's creating big bottlenecks for the other 5%. Our biggest worry isn't necessarily that we don't know how to customize, but rather that we won't have the resources to maintain customized code going forward; it's quite simple to update Rails as it matures versus the alternative. What have your experiences been with this problem? Have you found any best practices to avoid digging custom holes you can't climb out of?"

Comments

best Practice #1

[QuietLagoon]

Have you found any best practices to avoid digging custom holes you can't climb out of?"

.
Best Practice #1 - don't use Ruby on Rails. It is a dead end.

Re:Switch to django and python for starters

[ultrabot]

> The problem with django is that you have to use Python.

Can you explain the problems associated with using Python as a language for web development?

Don't you know that Python is just a hack that doesn't support "real" object oriented programming?

You can't just take a language like Python and make it object oriented by adding objects. You need a language like "Ruby" that is object oriented from ground up!

I read it on Ruby advocacy pages, and hence it must be true. Also, C00lDudeFromDaGhetto on IRC confirmed the same.

Nothing to see here, move along... and don't forget that RoR is much faster to development for than Java! And C!