Good point about the compile which I assume means static SQL access paths or does it?
But, for a small app, for the time being, wouldn't Net.Data be a good way to go that is easy to transition to .NET or Java when the app gets more complex or is a poor performer in the dynamic world? I say this because of what I saw from the example code in Net.Data books from IBM.
Thanks,
Dave
"Walden H. Leverich" <WaldenL@xxxxxxxxxxxxxxx> 8/7/2008 11:44 >>>
With performance like this, it seems to me that there's a case for
using RPG for heads-down data entry, transaction processing, and
any application where users demand top performance.
But performance like this isn't unique to RPG. It's achievable in most
web development languages if you're smart about how you code. Problem
is, many other web development solutions (MS being one of the worst
offenders) make is so easy to do big honking screens that encompass the
world that most "screens" aren't developed in a smart way.
RPG (along with Java and .NET) also have an advantage over PHP and Ruby
in that the former are static languages where you'll eat the compile
overhead once, where the latter are dynamic and you eat it each time. Of
course, dynamic languages have other advantages.
-Walden
--
Walden H Leverich III
Tech Software
(516) 627-3800 x3051
WaldenL@xxxxxxxxxxxxxxx
http://www.TechSoftInc.com (
http://www.techsoftinc.com/ )
Quiquid latine dictum sit altum viditur.
(Whatever is said in Latin seems profound.)
As an Amazon Associate we earn from qualifying purchases.