Thinking about languages for (re)writing DB applications....

Perl is quick to write and intuitive, once you get the hang of it.
It's said by some to be a "write once, read never" language, but
really with care and control, it can be readable.  Very cross
platform and cross database.

Java is big and taught by most Computer Science degree programs.
It takes object thinking to really use all it offers.  Very cross
platform and cross database, but that might be changing with MS
pulling out.  I understand it is very natural to use to write
multi-tier applications.  Does Java count as a vendor lockin by
Sun?

Cobol is what the staff knows.  There are two implementations for
Linux with lots of features (Percobol and Acucobol), but I'm
trying to avoid vendor lock in.

C let's you hang your self too easily (even though I like to write
in it).

There is Borland's Kylix and other tools for Linux, but I'm
trying to avoid vendor lockin.

There are a myriad of RAD tools from many vendors, but I'm trying
to avoid vendor lockin.

PHP and Python (and others) for doing web pages.  Got to write
the UI in something. Can the web be the only UI - does this
make any sense at all?

Richard
--
Richard L Gambrell, Senior Information Technology Consultant and
Director of Computing Systems and Networks
Information Technology Division, University of Tennessee at Chattanooga
Fax: 423-755-4150                Support Help-Desk: 423-755-4000
Direct phone: 423-755-5316       ITD Business Office: 423-757-1755
Mobile (urgent): 423-432-5122    Main UTC: 423-755-4111
Email: [log in to unmask]

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *