× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Hey Vern,

Maybe I misunderstood what I'm quoting, but here's the quote from Scott:
"I personally don't find any difference at all in difficulty or productivity between RDi and SEU."

I mean sure, I can still do my job in SEU, but at the same time I could also write code out on paper as well... I'd rather not, and just as I wouldn't take a job that had me coding on paper, I'd prefer to not be in a situation where I'd have to take a job that wouldn't let me use the IBM supplied IDE.

I know we all have our opinions, I was simply taking issue with Tom's take on Scott's opinion being more than opinion. (And I greatly respect Scott's knowledge, participation in the community, and his opinions... so I hope this isn't coming across to be the opposite.)

-Kurt
p.s. Scott's email that I'm referring to in it's total form, so the context of the quote is also presented:

Hi Charles,

Question, which one do you use? Given the nicely styled ILE RPG code
in HTTPAPI, FTPAPI, ect.. I'd think it would have been painful to
write either of those using SEU.

Both HTTPAPI and FTPAPI were entirely written in SEU. I don't find "styling" the code to be any more difficult in SEU than it is in RDi.
Indeed, for new code entry, I personally don't find any difference at all in difficulty or productivity between RDi and SEU.

I find that RDi is helpful in analyzing existing code, however... but as I said before, it's not the huge difference that folks on the forums advertise it as...

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.