Leon Rosenberg wrote: > well... maybe you are a totally cool development team, Awwww yeah.
Okay, not really ;) > following call stacks, debugging... distribution and so on > would be a real mess... but, as I told before, I never tried myself. > Call stacks are no issue. If you know the API and the chain of events I really haven't had any problems. > But what are the benefits for you to use ror? > _Extremely_ fast development cycles, _substantially_ smaller codebase. You see numbers like 10x thrown around; I wouldn't go that far, but at a minimum I personally see 4-8x in general and about a third the codebase. Code reviews are the same as in any language. Programmatic code checking in completely non-existent :( Refactoring support essentially non-existent, although I tend to need less, and with the smaller codebase they are less painful. Dynamically-typed languages may be harder to deal with in that regard. _Completely_ moving target: stuff is happening WAY too fast to keep up with. I do quite a bit of functional prototyping in RoR and then convert to J2EE, which makes some of my concerns go away since I'm using it primarily as a specifications document rather than an implementation model. Dave --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
