Re: Ruby On Rails on the iSeries

from: Pete Helgren <Pete@xxxxxxxxxx>

1.   You have to use the right tool for the right job
2.   There is no one tool you can use for every job

1. 85% of the applications my customers want are either A. Simple HTML 
CRUD applications used on an intranet for data maintenance or B. Simple 
web "self service" applications where data can be retrieved and 
updated.

2.   Another 10% are what I would call robust CRUD applications.  Lots 
of validity checking.

3.   The remaining 5% are what I would call "enterprise applications".  
In our case it will be payroll processing, student scheduling, month end 
closing, that kind of stuff.

+1 for the 'tools for the jobs' comment.  We have an 85/10/5 distribution
over the simple/robust/enterprise schema as well - but the 85 and 5 are
reversed from yours.  Nearly everything is at the enterprise level and that
is why we stick with iSeries RPG.  For the 5% 'keep track of my paper clips'
jobs, it is more than we need, but why break out and maintain a whole
infrastructure for such a small percentage.

Obviously, YYMV