Re: New to application programming... Please HELP!

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: Cor (non_at_non.com)
Date: 03/26/04 

Date: Fri, 26 Mar 2004 19:48:31 +0100

Hi Jim,

I am one from the time we had all to do with cables.

We did not have assembler, that was a great invention especially macro
assembler.

Than we got languages you know very modern, COBOL as you mentioned it did
stay a long time the most productive tool.

A long time later C was developed, for high school students, a toy, in real
environments not productive, so COBOL did stay on top.

Then we got Basic even more a toy for less educated people.

After that came Pascal because that basic was weird with those line numbers
which we where in the real programmer's world forgotten a long time before.

However, they did stay and none of the toys was as productive as the tools
before.

Real software was made by so-called 4th generation tools, with what you can
make everything you never did want to make.

Now we have dotNet with languages as C# and VB.net, both well chosen to be
good in more places than only the university.

In my opinion, this are again tools for the real programmer after COBOL to
make real productivity and able to beat the products made with 4th
generation tools.

However only my thought.

Cor

Relevant Pages

  • Re: Productivity
    ... Visual Studio 2005 is MUCH better than my productivity using the Fujitsu ... I really scorned VB for many years seeing it as being "kiddie programming". ... productivity shot through the roof when we began using it for our COBOL ...
    (comp.lang.cobol)
  • Re: Productivity
    ... Studio 2005 is MUCH better than my productivity using the Fujitsu IDE. ... Our productivity shot through the roof when we began using it for our COBOL code development. ... All of the housekeeping, fixed context, and overhead is hidden. ... I do know that there are tools that really integrate Windows with it (such as the ability to map drives to mainframe program files, interactive debug execute on the mainframe from the PC). ...
    (comp.lang.cobol)
  • Re: Productivity
    ... rewriting a COBOL application that originally took six weeks to develop. ... it is quite obvious that my productivity in Visual ... VS 2005 provides an Interactive Development Environment that is simply years ... them or send to a tab when you don't, intuitive context sensitive tooltips, ...
    (comp.lang.cobol)
  • Productivity
    ... Given that I am a newbie in C#, but am no slouch when it comes to COBOL, I ... it is quite obvious that my productivity in Visual ... VS 2005 provides an Interactive Development Environment that is simply years ... them or send to a tab when you don't, intuitive context sensitive tooltips, ...
    (comp.lang.cobol)
  • Re: PL/I Advantages
    ... The reason in COBOL's case, is that the USE of COBOL in IBM mainframe shops is ... processing" that is NOT available in COBOL (for productivity purposes) without ... As far as tools available for IBM Pl/I mainframe application development, ...
    (comp.lang.pl1)