> -----Original Message----- > From: tclug-list-bounces at mn-linux.org > [mailto:tclug-list-bounces at mn-linux.org]On Behalf Of Dave Sherohman > Sent: Wednesday, March 31, 2010 3:26 AM > To: tclug-list at mn-linux.org > Subject: Re: [tclug-list] Languages > > > On Tue, Mar 30, 2010 at 01:56:58PM -0500, Steve Cayford wrote: > > Jeremy wrote: > > >> There is no language that is "uber alles". The domain of the problem > > >> you're solving often points to the languages you might consider. > > > > > > Yes indeed. Each has pros/cons. > > > > > > > Don't forget COBOL. I guess that would be the domain of legacy banking > > systems. > > Good point: All languages have drawbacks, but this does not mean that > all languages have benefits. COBOL was the first language written to require structure and portability so that the same results could be obtained twice in a row or on separate computers, AND be maintained by folks other than the original coders. It was written in a day when "mainframe" computers often didn't have as much as 1 meg of RAM or 8 megs or hard drive due to the extreme expense (way over $100K). COBOL is now very old (60 years?), but it was and is very successful for what it was built to do. Eliminating "self-modifying code" was a big step forward. Grace Hopper aka "Amazing Grace" was the bulldog WAC or WAVE who made COBOL happen. She retired with the rank of Admiral, I think... very well deserved! Ada does the same sort of thing for a much more modern era of computers, and for technical as well as bean-counting software. Chuck