|
Paul, I hadn't seen that article before, thanks for pointing it. I think you are referring to Marty's quote, from MKS, one of our business partners: "you can really do native development faster [with RSE] than with SEU." This means that RSE is designed overall to make you more productive than SEU, even though little things here and there, such as opening a random member for the first time, may be "faster in SEU". But given the verifiers, and F1 help and content assist, iSeries Projects, and so on, over the course of a week you will be able to do more work with RSE than with SEU, once a certain level of competency is reached in the new tool set. That is, you should see an overall gain in productivity, making your overall development effort "faster" than it was with SEU. That is most certainly our goal, and what we have seen in the 11 years of CODE, even though it too had to deal to network latency for the initial file open, and didn't have the ability to cache the members between sessions. Hope this helps. Phil Coulthard, STSM, iSeries AD, IBM Canada Ltd. coulthar@xxxxxxxxxxx 905-413-4076, t/l 969-4076
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.