Re: Re: cost estimate for a GUI pilot

On this topic it really does end up being "to each his own". Some shops,
as they assess risk, conclude that moving to Ruby/PHP/Java/Node isn't worth
the risk. Others are already on board with it and assess the risk to be
worth it (maybe even based on where they are located). Lots of reasons to
weigh. I am greatly slanted towards Ruby/Rails because its community is
simply amazing. In the end it's not necessarily the language or web
framework - it's the community behind it. The other languages/frameworks
are watching and copying how Rails does things (i.e. Laravel** - arguably
the most popular PHP framework)

**http://laravel.com/docs/4.2 (see reference to Rails)

Regardless of existing shops adopting it I think the addition of new
languages to IBM i greatly betters the future of the platform. IBM
realizes this. Take a listen to Alison Buterill or Tim Rowe and how they
emphasize IBM i as a platform for open source development. Take a gander
at the YiPs wiki** and see all the continued open source efforts (much done
by IBM).

**http://youngiprofessionals.com/wiki

On final note, the biggest issue the platform has faced - access to a
machine for developers - is incrementally being solved. There are 37**
known IBM i cloud hosting providers. Entry level IBM i machines ready for
production workloads can be had for $500/month - that's getting decently
competitive given you get IBM i + DB2. That amount will be lessening in
the future as competition and innovation continue to happen.

**http://joehertvik.com/community-post-list-of-ibm-i-hosting-companies/

I've known Aaron longer than anyone on this list.. I can say that for

sure.

You've got me going down memory lane now :-) Learned lots from you. Good
times.


Aaron Bartell

On Mon, Nov 3, 2014 at 3:38 PM, Bradley Stone <bvstone@xxxxxxxxx> wrote:

RPG isn't driving the application. It's just pushing the info out there

to

be massaged by the common denominator in all web apps (ie, CSS, JS, etc).

What urging should be done is showing them what they can do with RPG. I
don't mind the other technologies either but most customers I deal with
want the "most comfortable" of the uncomfortable solutions. And that in

no

way means it's lacking in functionality.

What hurts it is equating RPG with green screens.

I've known Aaron longer than anyone on this list.. I can say that for
sure. I would never intentionally be "mean" to him. :)

I've seen them come and go over the years (Java, EGL, etc) and RPG is

still

here doing the work, and well.

Brad
www.bvstools.com


On Mon, Nov 3, 2014 at 3:26 PM, Nathan Andelin <nandelin@xxxxxxxxx>

wrote:

So why make it so difficult and keep pushing RPG/COBOL/Native

solutions

away?

Be nice to Aaron. He's doing a good thing bringing Ruby and Rails to

the

platform. Something needs to urge the RPG community from their comfort
zones - which in the case of green-screens is like being stuck in a

rut.

Add to that the technical debt accumulating in dead code and monolithic
design, and we really have a big problem.

Nathan.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing

list

To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing

list

To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.