I am working on a presentation about RoR. It's looking good except I cannot really find anything for a "Problems" section. There seems to be none. :)
Particularly I am interested in:
- What issues are there with maintainability/management when multiple developers are involved in large-scale RoR project?
- What specific considerations are there for developers on such large-scale projects using dynamically typed languages versus statically typed languages?
- Why might RoR not be suitable for large-scale projects?
I could not find anything on this googling the Internet. I would like to hear your thoughts about these points?
Thank you,
Arkadiy
I'm certain you can find a lot of this on the 'net, but I'm happy to oblige.
- Maintainability: Ruby and Rails are all about creating more maintainable code at the expense of a little performance. That's why Ruby is a dynamic language in the first place. As far as developers/teams are concerned, Rails is great for creating and maintaining code that is easy to understand and maintain.
- Dynamic vs Static: From the perspective of a development team, static languages have a the unique advantage of being very explicit. There isn't magic to confuse new developers, and there should be little work in terms of chasing down ghosts (in theory, anyways). That advantage is quickly outweighed by the ability of a dynamic language to really take advantage of OOP and get started developing quickly.
- Suitability: I can't think of any good reasons. It's test-driven, proven, and extremely well designed. It was made to do the job, so it doesn't surprise me that this is the case. :)
Menu
709
