|
Trevor, Apologies - the "as any fule know..." comment was meant in jest - it's a quote from Molesworth. Maybe your bike is more robust than mine :-) But regular service on a server can't necessarily catch all the problems with WAS/Apache/Tomcat (at least not in my experience). The web versions of our apps have more problems with communications than do our green-screen apps. Modular architecture can be good from the point of view of maintenance, but it adds more complexity in terms of the number of 'moving parts'. At least with a green-screen app, any of your RPG coders can have a crack at it if it needs changing. Many companies aren't as forward-thinking as yours - timesheets are still handwritten in many (most?) places. My "neither the time nor the resources" coment still stands. Some may call it inertia. But I don't think my Jave vs. RPG comment was out of place. There are many people who look at our RPG apps and say "But this can be done better/faster/nicer using <insert other language/technology here>". Even in the cases where this IS true, why would a company spend time, money and resources fixing something that, as far as THEY are concerned, ain't broke? If they;'re willing to provide jobs for data-entry clerks and RPG programmers, I have no problem with it. Rory
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.