Re: Change management systems

["Timothy Adair" <tadair@xxxxxxxxxxxxxxxx>]

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.