Re: cloud services with new development on IBM i on Power

Pete,

We must have used some of the thousands of API's that didn't change across the boundaries from Windows 95 to Windows 2012 and .Net versions.

Some of our older VB and VB.Net apps have worked all the way across the spectrum of OS's and .Net releases including our code that uses JT400.DLL to talk to the i. JT400 rocks in .Net :-)

Now of course if you've built apps in MS Office, mileage may vary :-)

Just because all i is your religion, don't spread FUD, unless you're just relaying your personal experiences, but call it that because you're representing perhaps a small minority of developer experiences and perhaps your own.

i, Windows or Linux in the cloud, Pick your flavor :-)

I'm starting to find that catchy.

Regards,
Richard Schoen
RJS Software Systems Inc.
Where Information Meets Innovation
Document Management, Workflow, Report Delivery, Forms and Business Intelligence
Email: richard@xxxxxxxxxxxxxxx
Web Site: http://www.rjssoftware.com
Tel: (952) 736-5800
Fax: (952) 736-5801
Toll Free: (888) RJSSOFT


-----Original Message-----


message: 1
date: Thu, 16 May 2013 17:58:11 -0500
from: Pete Helgren <pete@xxxxxxxxxx>
subject: Re: cloud services with new development on IBM i on Power

The first item you found humorous is, I am afraid, quite common. Anyone who has been on the MS treadmill knows that each major version has a hit on end users or development. Either the UI has changed or the API's are radically different: Office 2003 vs Office 2007/10/13, Access 2000 vs Access 2003/10/13. As a MS developer and former MS marketer, I experienced WAY to much pain when our friends in Redmond decided to change API's with no backward compatibility. Their UI's, API's and licensing changes, seemingly on a whim, made the move to Java and PHP SO much of a gift that, outside of occasional contract work on .Net applications I stick with RPG, Java and PHP, all of which run on i (and on Windows 2000 thru Windows 8 - can you say that about VB.net apps developed in 2000?)

So yeah, I have a customer running a Power 7 box with IBM i 7.1 running apps with some components developed in 1985 along with Java and PHP apps. They have a Windows server stuck at 2003 and MSSQL 2005 to support some applications that cannot move. This is real world and worth comparing.

What I like best about the comparison is not so much the horsepower comparisons as to WHY there might be any applications STILL running Windows 2003 and MSSQL 2005: Why, because MS doesn't care about you retaining your investment. Short term gain == long term pain when you partner with Microsoft. You may not feel it, but your customers will.

Pete Helgren
www.petesworkshop.com
GIAC Secure Software Programmer-Java

On 5/16/2013 4:11 PM, Matt Olson wrote:

1. They use the latest software of IBM I, and compare it to Windows 2003 in a report that came out in 2010!!! Why are they using such an OLD operating system and database platform (SQL 2005). This is like comparing IBM I Power 7 box to a 286 running DOS. Of course IBM I would win when you make these kinds of comparisons. At this point in time SQL 2008 R2 and Server 2008 R2 were out at the time, they could have virtualized everything without buying VMWare, and setup a cluster with built in software to the OS. But instead they decide to purposely make IBM i shine by making terrible comparisons.