|
On Mar 6, 2017, at 5:33 PM, John Yeung <gallium.arsenide@xxxxxxxxx> wrote:
On Mon, Mar 6, 2017 at 4:31 PM, Buck Calabro <kc2hiz@xxxxxxxxx> wrote:
On 3/4/2017 12:55 PM, Brian Parkins wrote:
I know scores of IBM i developers who would _love_ to have RDi on their
workstations. Sadly, the costs kill the argument. This in turn is doing the
IBM i platform no good at all.
Having lived through the WDSC 5 era, I'm more cynical than you are.
WDSC 5 was bundled with the compilers. In other, bitter, words we as a
large statistical cohort of IBM i developers literally wasted our
employers' money rather than use WDSC.
I don't disagree with the "wasted money" part of that, but I would
have framed it differently. You make it sound as though we
statistically *refused* to use it.
Sure, some people complained that it was too buggy or too slow or what
have you. Whatever their reasons, they did make the choice to stick
with SEU and reject WDSC.
But I strongly suspect that a much larger portion of the midrange
community simply didn't know anything other than SEU existed. If I'm
right, it wouldn't be fair to call it a choice. I can hear the
choruses of "it's up to everyone to keep themselves abreast". Maybe
so. But I still think there is a qualitative difference between making
a deliberate choice versus not knowing there is a choice.
John Y.
--
This is the Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries (WDSCI-L) mailing list
To post a message email: WDSCI-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/wdsci-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.