**Repost with Updated Subject**
What should each shop do ? That's the hard part. I've been wrestling that question for the past 10 years and keep coming back to: "It all depends."
I've been with 2 groups just this week who think Node.Js is the answer to their aging RPG developer population.
Could you imagine writing all your business logic in Javascript....Yeai.
Maybe leave business logic in RPG and go to Node. That's more palatable perhaps because Node is really just the front-end to the services then.
And others think Python, Java, Ruby, PHP and the permutations go on.....
Here's my biggest question and I don't have answers to it:
Should a shop adopt a single language strategy going forward or maybe 1 or 2. Or is each app best of breed ?
In most shops I am seeing a mix of all of it. Not sure if we can ever get the cat back in the bag.
One client I was at have flagged the RPG guys as a huge business risk. So then what...new packaged software, put node or some other gui on the front of everything and then when the wind changes redo it all again.
These are all vexing questions when trying to adopt a future-state strategy.
My personal favorite thoughts for IBMi folks are:
-Keep your core business logic in RPG, assuming home grown and/or have source code. Don't kill the business on an ERP refresh unless it will help the business grow without grinding to a halt in the process.
-Decide if you still want 5250 or 5250 scraped UI or an all new UI layer for user interfaces.
-Plug in external automation and integration where it makes sense.
-Give your execs some sort of decision support even it it's a poor mans dashboard.
Regards,
Richard Schoen
Web:
http://www.richardschoen.net
Email: richard@xxxxxxxxxxxxxxxxx
Phn: (612) 315-1745
------------------------------
message: 3
date: Thu, 18 Apr 2019 08:53:02 -0500
from: Joe Pluta <joepluta@xxxxxxxxxxxxxxxxx>
subject: Re: Mono on IBM i - Porting Mono to AIX and IBM i
I don't want to make this just about my shop, Richard.? I'm trying to create a generic roadmap to get Mono into traditional IBM i shops.? If you have Microsoft development skills, enthusiasm, and time to try new things, I don't think this is a hard sell.? I'm trying to see how to make it attractive to the large number of shops that are maintaining existing business applications and may have, at most, one champion for new technologies.? Plenty of people who read this list have trouble getting RDi into their shops, much less a new technology like Mono.? So how do we get those lone early adopters to use their limited time on Mono?
Again, I don't want to make this about me.? At my shop, I can do everything right up to step 7, it's just a judgment call on my part as to whether it's worth the effort. But there are lots of shops that have one developer who's struggling to get coworkers to use RPG /free; in fact, that's a large part of my audience.? How can we help them take the plunge into Mono, and does it even make sense for them?? If you think success is predicated on demographics and enthusiasm level, then maybe Mono isn't for everybody.
midrange.com
