Re: RdI vs SEU was: RE: Change management systems -- WDSCI-L

Kurt

Scott didn't say, as you misquoted him, "...SEU is no different in RDi in regard to productivity..." - he said something more like "...the advantages...are being constantly overstated in these forums..."

Those are completely different. I agree with the latter. Do I use WDSC+? Of course. Do I find it super-productive? Naw. Does it help me do things it'd be less simple to do in PDM or SEU? Sometimes. But there is still nothing as good for merging changes as option 55 in PDM. That just isn't available in WDSC+.

So you use the tool for the job that best fits it. Both green-screen apps and graphical/browser/thick client apps have their place.

I'm just sayin'!
Vern

Kurt Anderson wrote:

Tim,

How is Scott giving his opinion cutting through opinions and getting to the heart (Fact?) of the matter. It's not, it's an opinion. I mean, I don't like disagreeing with Scott on this matter, but I do. He has said that to him SEU is no different in RDi in regard to productivity. Well, I guess that's great for him, but without a doubt the number of lines viewed and number of columns viewed (on my computer and at a co-worker's, who may not have the emulator display set to 132 width) those are extra keystrokes. Extra keystrokes that are required to grasp the big picture.

To give an example of just how beneficial I find WDSCi to be over SEU:
Maybe I'm shooting myself in the foot here, but when I was looking for a job just over a year ago, I had considered entry-level java programmer positions instead of taking an RPG job coding in SEU. Luckily, I landed in an environment that allows (and since, embraces) WDSCi as well as more modern programming practices (modularization - not sure if that's really "modern" in the world of programming, but definitely in the world of RPG).

-Kurt
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Timothy Adair
Sent: Friday, March 12, 2010 4:04 PM
To: midrange-l@xxxxxxxxxxxx
Subject: Re: Change management systems

Thank you Scott!

Finally, someone cuts through all the opinions (on both sides) and gets to the heart of the matter.

If programmer ABC writes the program in SEU/PDM and programmer XYZ writes it in WDSc/RDi, and the user sees and runs the exact same program, who cares which programming environment it was written in? (Pardon the bad grammar.)

Perhaps we need to remember that our primary purpose as developers is to support the user. Period. Every user - from the data entry operator to the CEO.

Now that I'm done ranting, allow me to ask a question. Does compiling the same source in PDM produce the exact same object as compiling it in WDSc/RDi?

"Scott Klement" <midrange-l@xxxxxxxxxxxxxxxx> wrote in message news:mailman.14503.1268429052.2580.midrange-l@xxxxxxxxxxxxxxx

Technically, PDM and SEU are not the same thing. But, PDM calls SEU when it needs to edit code.

They both come together as part of a package named ADTS. (Application Development Tool Set) along with a few other things.

Personally, I think the advantages of WDSC/RDi/RDP over PDM/SEU are being constantly overstated in these forums. There are certainly some things that RDi does better, like copy/paste, outline view, syntax highlighting.

But these things aren't the ultra-awesome, revolutionary things that folks in these forums make them out to be. Yes, copy/paste is better in RDi, but I could still do it in SEU, and I could do it pretty well. Yes, outline view is useful, but searching out what I'm looking for also works. Yes, syntax highlighting/coloring can be nice, but I can read my code okay when it's all one color.

Personally, I think the user interface seen by the USER is far more important than the interface seen by the DEVELOPER.