
Originally Posted by
R.Daugherty
Interesting points I'd like to counter, also thanks to jeffolen4 for throwing it out there for comment to start with.
While I still prefer SEU, I also have WDSc or rdi or whatever the heck it's called this week, and I use whichever based on project. There is absolutely no call for referring to a text IDE (SEU) as you did when everyone has the Eclipse RPG IDE which is very robust. I used it last year for developing an RPG and Java mix app, instantiating Java classes and calling methods from RPG, bouncing back and forth between two views in the IDE. It should be obvious to you that we have as advanced IDE as anyone else.
Concerning new development with GUI, there's a thing called the Apache web server which seems to be used a lot out there. It's on the iseries. The Eclipse RPG IDE is geared for developing for it and other non-GUI web services. What do you think other people are doing out there fir "GUI", and why do you think they somehow have something we don't?
Now on to your and OP's grudge against RPG programmers. I can make some observations:
Non-trivial businesses have been running on RPG for decades.
Features since RPG/400 are mostly aethestics; it is arguable, and an argument I don't have the time to engage in, on the benefits of certain modularity aethestics, culminating in OO architecture. There are extremes in monolithicism and extremes in layers of modularity.
The right mix was found by RPG/400 days in callable programs. For most every architecture feature we have now we have always been able to do it pretty well, and very fast. Some things make it easier and some more obscure, but our success was based on a great OS/400 language architecture from the beginning.
When a business is running on a set of code, consistency is more important than fanbois of new things because they're excited about it. That's personal and to be expected, it's your career, but what businesses do to stay in business and keep costs down by using what works is irrelevant to what you want to do personally. If the business is happy and the programmers are happy, it's really none of your business to criticize them as in this thread. What they have works, what they do works, and unless you come up with something better, and believe me, for everything you fanbois think is better there are tradeoffs, then they'll keep using it what works until a clearly superior cost effective way of doing things is determined to be used.
And for all the talk, I haven't seen that clearly superior cost effective way fo doing things. Lots of talk about PHP for example, and non-trivial businesses are not running on that.
That's pretty telling right there.
rd