Re: WDSC changing to RDi

Oh don't get me wrong. I just started dot net. I expect MS to do
something to me. All I'm saying is that there are a lot of us they tried
very hard to get the old green screen coders to use WDSC, and some of the
points we made were: it's free, it's good to develop in, it's supported by
IBM, etc etc. Then IBM goes a makes liars of us by now charging for it.
If a shop decides they don't want to spend any money, where does that
leave the developers? Going back to the green screen and SDA? It's like
a kick in the teeth to all those that shouted their praises.

And I'm quite sure within a year I'll be more than a little bewildered by
MS too. After all, they did earn the nickname MicroShaft... lol.

Ron Power
Web Application Developer
Information Services
City Of St. John's, NL
P.O. Box 908
St. John's, NL
A1C 5M2
709-576-8132
rpower@xxxxxxxxxx
http://www.stjohns.ca/
___________________________________________________________________________
Success is going from failure to failure without a loss of enthusiasm. -
Sir Winston Churchill
Freedom is the right of all sentient beings. - Optimus Prime



Joe Pluta <joepluta@xxxxxxxxxxxxxxxxx>
Sent by: java400-l-bounces@xxxxxxxxxxxx
2008/03/31 12:03 PM
Please respond to
Java Programming on and around the iSeries / AS400
<java400-l@xxxxxxxxxxxx>


To
Java Programming on and around the iSeries / AS400
<java400-l@xxxxxxxxxxxx>
cc

Subject
Re: WDSC changing to RDi






Ron Power wrote:

Way to go IBM, loyalty bonus points... NOT.

It's nearly April, so I can rant on this one. But it will be a short one.

If you are comparing IBM customer loyalty to Microsoft, in my opinion
you are missing the boat badly. I've developed for Windows over the
years, and I've followed the travails of other Windows developers. Work
with Microsoft for a few years, and wait until they change either the
operating system or the tools such that your existing code base no
longer works.

I'm not saying they will; it's possible that they've managed to
stabilize things with .NET and Vista. However, history shows that
Microsoft has no problem throwing its developers under the bus. A prime
example of this was the VB.NET rollout. VB6 programmers got trashed.
Try converting VB6 programs to VB.NET; it ain't easy.

Anyway, enough from me. If you really think Microsoft is a good way to
develop applications, then that's your opinion and it's hard to argue,
and certainly VS.NET is a nice package. Personally, I'm really
beginning to prefer the open source stuff. Since I'm working very hard
to remove my dependence on Microsoft software (I'm currently about 33%
of the way there), you have to take my opinion with a grain of salt
<smile>.

Joe