|
IBM Decided to spend their money on one tool that has vastly more
capability and more opportunity for enhancement. It's also based on
tools used for other languages so it's familiar to many many more
developers than SEU.
Were IBM to continue to maintain both tools there would be either fewer
features in RDi or both it and SEU would be more expensive.
And there is no force. You can continue to utilize SEU for your editing
you will simply find that you are becoming less and less efficient while
with RDi you become more and more efficient.
IBM Quit manufacturing AS/400s and then iSeries and then System i. They
didn't do so to force you to buy a Power System they did so because
Power Systems are far superior in capability and performance. You can
still run an AS/400 (and some DO!) but you'll spend much more money for
the same performance.
As to the cost, that argument doesn't hold water for me. It's like a
builder who refuses to purchase an air-nailer for his carpenter because
it's expensive and the hammer he already owns still works.
- Larry "DrFranken" Bolhuis
www.frankeni.com
www.iDevCloud.com
www.iInTheCloud.com
On 4/18/2014 12:00 AM, Alan Campin wrote:
No, IBM decided to force people to buy RDi by stopping to update SEU withwrote:
new releases. I am using at work great but you have to buy and a lot
companies won't buy.
On Apr 17, 2014 9:49 PM, "John Yeung" <gallium.arsenide@xxxxxxxxx>
wrote:
On Thu, Apr 17, 2014 at 11:16 PM, DrFranken <midrange@xxxxxxxxxxxx>
becauseThere was a time when IBM created FSEDIT. It was warmly welcomed
bigit was such an improvement over the SEU of the time.
Now we get awesome tools like RDi and we bash them? I don't get it.
I don't see anyone actually bashing RDi, so I guess you mean folks are
bashing IBM. Well, perhaps the situation is different now, but I
don't know. Was FSEDIT expensive and SEU out of date with respect to
the compiler?
John
On 4/17/2014 10:49 PM, Alan Campin wrote:
SEU frozen at v6r1. Anything above that level will not work. Stinks
list--time. Have to get RDI if you want syntax checking.
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
--To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
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.