× 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.



In my case, I'm at least 20% more productive in RDi, because I haven't willingly used SEU since 1993. In addition, I haven't used SDA or RLU since 1999. After all these years, I'd be more comfortable writing a novel in Notepad than writing code in SEU. Just the idea that I can't press F1 to find the parameters of a BIF or find out which indicator means what on some obsolescent fixed-format opcode gives me the heebie-jeebies! I accept that in your situation you don't see a big gain, but please don't call me a liar for having a different experience than yours.

Dave Shaw
Sent from my Windows phone

-----Original Message-----
From: "Scott Klement" <rpg400-l@xxxxxxxxxxxxxxxx>
Sent: ‎4/‎3/‎2015 3:09 PM
To: "RPG programming on the IBM i (AS/400 and iSeries)" <rpg400-l@xxxxxxxxxxxx>
Subject: Re: RDi vs SEU

I'm definitely NOT 5% more productive on the whole. There might be
certain circumstances where it makes me 5% more productive... but
there are also circumstances where I'm more productive with SEU.

I find it very, very hard to believe that anyone is 5% more productive
with RDi on the whole.

And any circumstance where someone says something like 20% or higher...
they are lying to you to try to sell something, because that's just
totally absurd.


On 4/3/2015 10:45 AM, Jon Paris wrote:

Is there anyone on this list who would not claim that they are as a
minimum 5% more productive with RDi once past the initial hump?



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.