Re: WDSC vs. RDi

David Gibbs wrote:

Well, from my perspective (as a System i developer), WDSC is a tool for System i developers. So the *most* important components are RSE, LPEX, SEP debugger, etc.

Whoa, whoa, whoa - this is an argument that doesn't need to happen! I'm not trying to change your perspective, just pointing out that your perspective doesn't include the bulk of what was in WDSC.

The other tools: HTML editor, JSP editor, web site designer, etc, are not all that important to most System i host application developers.

And see, this is a new phrase: "System i host application developer". It's a euphemism for green screen developer, and it's something I thought we were trying to get rid of, and that's really my point. WDSC made web development tools available to the System i developer without pigeon-holing him into the green screen role. I thought this was a great step forward for System i development in general, because it gave green screen dinosuars like me a free set of tools - and more importantly, tutorials and samples - to allow me to extend my skill set. The unbundling of the RDi package negates that.

The fact that the System i specific components are only a fraction of the package is meaningless ... they are the MOST important part of the package to a System i developer.

No. I am a System i developer, and I use all of those tools all the time. I am no longer a "System i host application developer", and if we want to see the platform move forward, we need lots more programmers to lose the "host application" designation. Haven't we all agreed on that a long time ago?

RDi basically contains all the WDSC components a System i developer needs and eliminates the components they don't necessarily need (at least for host application development).

And I consider it a blow - not fatal, but painful - to the future of the platform, because there are a lot of green screen programmers who will never play with the web stuff now.

JMO, obviously.

And mine.

Joe