« Adding the Right New Technology | Main | IBM i: A Competitive Advantage »



Feed You can follow this conversation by subscribing to the comment feed for this post.

R A Valencourt

Why do you (and almost all articles that I read about the history of the IBM i) say that it began with the AS/400 twenty-five years ago, when it began ten years earlier with the announcement of the S/38?

C. E. Wise

Let's not forget about the S/32, 34, and 36.

Wim Esbach

There is no difference between explaining PF3 and the Esc key with any new employee. Same goes for PF24 and the multiple tabs that show and hide the buttons in an information bar.
Don't suggest some things are old and others are modern. It is all perception. Same as Apple software was known from old the 5250 interface shines in its consistancy from a UX point of view. Learning once and applicable to all other applications. With the new forrests of mobile applications we find ourselves again at a setback with scores of programmers needing to learn to adhere to GUI standards and allow for consistent UX across a range of applications or a single application in particular. Copyright laws will ensure there will remain differences between brand platforms. As such there shall always be learning curves for newcomers.
I applaud the 5250 datastream, but also the helptext architecture as supported on the AS/400, the consistency of basic functionality in the UX (as exit and refresh) and even the type-ahead keyboard buffer. It will take a lot of time for such standardisation to come to our new application platforms.

Wim Esbach

I do think S/36, 34 and 32 are different beasts though grom the same family. The S/38 was the first one of "i-Series blood".
And what a noble bloodline it is. Of course 25 years stoll sounds young enough while 35 years sound of age already.
It's up to the PR department to make the most beneficial choice.

Henry James

Character screens (mine are never green and black) provide a consistency, simplicity and most of all speed and accuracy for commercial data input which remains way ahead of all the GUIs. No mouse, fingerpointing or whatever, just fingers on the home keys and input.
When the input comes downstream from an EDI or whatever, even the input is reduced to a set of commands / menu selection.
professional designers and developers need to recognise and use the strengths of each variety of interface.

The comments to this entry are closed.