Geez… who would have thought that you had to mess around with engines
and the like just to share code?? thats 1 thing thats easier in java.
Coming from a java background, I don’t find code sharing harder in
Rails than J2EE. Using plugins to share library code scales very
well, right from a few shared methods up to large code libraries.
Certainly no more difficult than using jars.
If you want to share more than just ruby code (including controllers
and views), then as James says, engines provide a sort of ‘super
plugin’ system. I don’t know of any equivalent facility in J2EE.
I suppose this is why ROR is sometimes said to be not very scalable?
Any comments on this?
I NEED to convince my boss that ROR is scalable (in terms of size not
number of hits). Any ideas what i can say? I write enterprise
(debateable) software for our organisation.
Rails tries as hard as possible to be as concise as possible, so you
never have to write more code than you need. This results in far less
code for the same functionality as you’d write in J2EE (rough
estimate, less than half the code). Less code = less maintainance.
Rails also makes it extremely easy to write both unit and functional
tests, building confidence into your code as your application gets