Re: George Farr declares featurespecificpricingonhorizonfor WDSC

[Booth Martin <booth@xxxxxxxxxxxx>]

I should have prefaced my remarks, both earlier and now, with this 
disclaimer:  I like VARPG from IBM.  I spent a few years learning how to 
use it and thinking in event-driven instead of cycle-driven design.  I 
spent a great deal  of my own time and energy on VARPG, and loved every 
bit of it.  I installed several applications that, so far as I know, are 
still running.  The users loved the interface, and mangers were getting 
information in ways they'd never seen it.

*But* VARPG never gained traction.  Career wise my efforts were a 
complete frustration and waste.   Great product, great solution, but 
everyone wanted Java.  I could deliver a working application before Java 
designers even had their test bed completed, but so what.  They wanted Java.

So can you blame me if I get a little miffed when I see someone write 
that IBM didn't deliver a thick client?

Anyway,

I am sure there are a lot of reasons that VARPG didn't gain traction but 
IBM's commitment to it isn't one of them.

However, VARPG from IBM is native Windows, does run well, is easy to use 
for an RPG developer, and it is thick or thin client, depending upon how 
it is deployed.  It is not Java, it is not simulated Windows.

Let me repeat:  VARPG is native Windows.


The fact that the software runs a release or two behind is no real deal 
breaker for very many RPG developers, I am sure, as most developers do 
not get up to speed with new features for at least a year or so.



albartell wrote:
> Being that you know so much about me and what I will and wont use... :-)
>
> What exact IBM technology are you talking about?  
>
> I am guessing you mean VARPG, which I wouldn't count as 'native' because you
> essentially have RPG.NET (ASNA) as far as I can tell.  And if memory serves
> me right, VARPG doesn't keep up to date with the latest releases of the RPG
> complier which gives obvious indication of how IBM views the product.  I am
> sure there are a number of other drawbacks with VARPG just as there are with
> Webfacing (read Java).  I want to re-emphasize that if it isn't native it
> wont last.  Of course if we are running "thick client" something has to NOT
> be native, but that is where the smart client concept could come into play
> (http://en.wikipedia.org/wiki/Smart_client).
>
> To expound on my dreams of RPG, this thick client capability would use the
> concept mentioned above (i.e. smart client) and would simply give the RPG
> programmer a set of UI components that are created and fully supported by
> the RPG compiler team.  There would of course be a new version of DSPF DDS
> that looks nothing like it's fore fathers (more so for broad programmer
> acceptance - which would mean free form would be essential, or rather
> anything non-cryptic). 
>
> Aaron Bartell 
>
>
> -----Original Message-----
> From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On
> Behalf Of Booth Martin
> Sent: Monday, March 26, 2007 12:32 PM
> To: Websphere Development Studio Client for iSeries
> Subject: Re: [WDSCI-L] George Farr declares
> featurespecificpricingonhorizonfor WDSC
>
> You already have the thick client solution, and have for over 10 years. 
>   Its RPG, its easy to migrate your applications, and it uses your existing
> data and skill sets.
>
> But you won't use it.
>
> albartell wrote:
> ...
> > Imagine having a RPG native way to create browser and thick client 
> > apps from the iSeries!  The probability of this happening 'natively' 
> > is less the more I hear George talk though.  ...
>
> --
> ---------------------------------
> Booth Martin
> http://www.Martinvt.com
> ---------------------------------
> --