Author Topic: The worst programming language ever  (Read 14767 times)

0 Members and 1 Guest are viewing this topic.

Online MIS42N

  • Frequent Contributor
  • **
  • Posts: 563
  • Country: au
Re: The worst programming language ever
« Reply #25 on: November 06, 2021, 02:52:58 am »
COBOL was right for the times. The compilers produced small efficient programs that could produce payrolls for 25,000 employees on a computer with 64kbyte and an instruction time of 2us. Because of the verbosity, it wasn't difficult to maintain. Not quite self documenting like Grace Hopper wanted, but close. The PIC(ture) reservation of memory is better tuned for portability than most languages because it described what the programmer really wanted rather than what the machine provided. I want to store up to a million dollars as credit or debit, in a computationally efficient manner, PIC S999999.99 COMP. And let the compiler figure out how to deal with that in whatever architecture it ran on.

Many people criticise COBOL for being slow to write, due to the verbosity. I haven't written a COBOL program for over 30 years, but in the day I could churn out between 200 lines a day to 100 lines an hour. Like any language the effort is in translating the ideas into actions and it doesn't really matter in what language that action is expressed. For one employer I wrote programs that were COBOL, FORTRAN and Assembler composites to take advantage of the computational features of FORTRAN, the ease of laying out a report in COBOL, and Assembler routines to compress and decompress records being written to and read from magnetic tape.

Today such efficiencies are no longer prized. Throw more memory and a bigger processor at the task. The C language changed a lot, now the choice for more efficient programs. And if efficiency is subordinate to productivity , choose the language appropriate to the task at hand. The worst programming language is the one that gives the most grief trying to translate ideas to actions. It may be possible to compute satellite orbits using COBOL, or write invoices using FORTRAN. Who would want to.
 
The following users thanked this post: nctnico, newbrain, Just_another_Dave

Offline Just_another_Dave

  • Regular Contributor
  • *
  • Posts: 205
  • Country: es
Re: The worst programming language ever
« Reply #26 on: November 06, 2021, 08:37:51 am »
The main critique of programming of course is largely not so much the language (not that bad ones are any help, mind), but the environment in which it's placed.  COBOL is bad, but it's particularly notorious because of its crusty, ancient, mainframe-centric development environment (if you can call that "development").  Dev, deployment, scaling whatever, those are the real problems -- from any language.

Thankfully, COBOL development tools have improved a lot outside the IBM world. Nowadays it isn’t uncommon to develop COBOL programs using a version eclipse (or other modern IDE). Sometimes, they even test programs in normal windows machines before uploading them to the mainframe (there are compilers for both windows and Linux). And just in case you need to program a front end for the backend that runs in the mainframe, some companies offer tools for developing mobile phone apps in cobol, as well as visual cobol (like Visual Basic but using cobol)
 

Offline SiliconWizard

  • Super Contributor
  • ***
  • Posts: 17841
  • Country: fr
Re: The worst programming language ever
« Reply #27 on: November 06, 2021, 06:34:53 pm »
The main critique of programming of course is largely not so much the language (not that bad ones are any help, mind), but the environment in which it's placed.  COBOL is bad, but it's particularly notorious because of its crusty, ancient, mainframe-centric development environment (if you can call that "development").  Dev, deployment, scaling whatever, those are the real problems -- from any language.

Thankfully, COBOL development tools have improved a lot outside the IBM world. Nowadays it isn’t uncommon to develop COBOL programs using a version eclipse (or other modern IDE). Sometimes, they even test programs in normal windows machines before uploading them to the mainframe (there are compilers for both windows and Linux). And just in case you need to program a front end for the backend that runs in the mainframe, some companies offer tools for developing mobile phone apps in cobol, as well as visual cobol (like Visual Basic but using cobol)

Yes, I've seen modern IDEs, tools and libraries for COBOL.
The thing is - if we consider COBOL as a general-purpose language, it would be horrible. But it's not meant to be one.

While domain-specific languages were rather common back then, these days, they tend to be frowned upon in general regardless of their merit. We tend to favor general-purpose languages whatever the application, for a number of reasons, including of course the ease of finding developers and replacing them.
 
The following users thanked this post: Just_another_Dave

Offline Just_another_Dave

  • Regular Contributor
  • *
  • Posts: 205
  • Country: es
Re: The worst programming language ever
« Reply #28 on: November 06, 2021, 08:52:15 pm »
The main critique of programming of course is largely not so much the language (not that bad ones are any help, mind), but the environment in which it's placed.  COBOL is bad, but it's particularly notorious because of its crusty, ancient, mainframe-centric development environment (if you can call that "development").  Dev, deployment, scaling whatever, those are the real problems -- from any language.

Thankfully, COBOL development tools have improved a lot outside the IBM world. Nowadays it isn’t uncommon to develop COBOL programs using a version eclipse (or other modern IDE). Sometimes, they even test programs in normal windows machines before uploading them to the mainframe (there are compilers for both windows and Linux). And just in case you need to program a front end for the backend that runs in the mainframe, some companies offer tools for developing mobile phone apps in cobol, as well as visual cobol (like Visual Basic but using cobol)

Yes, I've seen modern IDEs, tools and libraries for COBOL.
The thing is - if we consider COBOL as a general-purpose language, it would be horrible. But it's not meant to be one.

While domain-specific languages were rather common back then, these days, they tend to be frowned upon in general regardless of their merit. We tend to favor general-purpose languages whatever the application, for a number of reasons, including of course the ease of finding developers and replacing them.

Successful languages tend to end up finding their own niche. The idea of having a general purpose language that can be used for anything seems great while you’re learning your own language, but after learning several languages I realized that each type of application has its own needs and having a standard library that helps you with them saves a lot of time. However, most new languages try to innovate in their sintaxis or supporting any type of programming paradigm instead of providing better tools for a certain niche, which seems to make them a solution looking for a problem to solve instead of something worth your time (until third party libraries make it useful for a particular domain)

I wouldn’t use cobol for developing a simulator, but neither I would use C++ for programming a website
 
The following users thanked this post: newbrain, james_s

Offline mikerj

  • Super Contributor
  • ***
  • Posts: 3671
  • Country: gb
Re: The worst programming language ever
« Reply #29 on: November 14, 2021, 05:12:42 pm »
JavaScript, Python, and Java have a *lot* more people writing code in them than C/C++ do.

Overall sure, because that encompasses a huge amount of web/desktop programming.  Look at microcontroller development and the situation is reversed.
 

Offline NorthGuy

  • Super Contributor
  • ***
  • Posts: 3583
  • Country: ca
Re: The worst programming language ever
« Reply #30 on: November 21, 2021, 09:40:40 pm »
Perl was widely used. It wouldn't survive a second in Today's world :)
 

Offline Saskia

  • Super Contributor
  • ***
  • Posts: 2893
  • Country: de
  • you unlock this door with the key of imagination
Re: The worst programming language ever
« Reply #31 on: November 21, 2021, 09:46:24 pm »
actually I kinda liked make (the original one) and using awk and sed plus variables in the target declaration. It made for very compact and fast code. Which was what I was paid for. It took my successor about 2 years to replace my 64 lines of code.
 

Offline SiliconWizard

  • Super Contributor
  • ***
  • Posts: 17841
  • Country: fr
Re: The worst programming language ever
« Reply #32 on: November 21, 2021, 10:19:29 pm »
Make is still widely used, and although I personally don't use the latter, I believe awk and sed too.
Even many of the more modern build tools (such as CMake) generate makefiles, and make does the real job. :-DD
 

Offline brucehoult

  • Super Contributor
  • ***
  • Posts: 6464
  • Country: nz
Re: The worst programming language ever
« Reply #33 on: November 22, 2021, 12:22:23 am »
Perl was widely used. It wouldn't survive a second in Today's world :)

I use Perl every day. It's a superset of both sed and awk, and runs faster. It's perfect for 1-100 line scripts where Python looks like COBOL in comparison.
 

Offline brucehoult

  • Super Contributor
  • ***
  • Posts: 6464
  • Country: nz
Re: The worst programming language ever
« Reply #34 on: November 22, 2021, 12:25:35 am »
Make is still widely used, and although I personally don't use the latter, I believe awk and sed too.
Even many of the more modern build tools (such as CMake) generate makefiles, and make does the real job. :-DD

"make" does two very different jobs:

1) describe the dependencies between files, and the actions to update them, in a concise, powerful, understandable, and maintainable way.

2) execute the dependency graph as quickly as possible using the available resources

Make does a pretty good job of 2), though ninja is better.

Make does a lousy job of 1) by modern standards. There are many better options now. And, yes, those better options often use make or ninja as the execution engine.
 
The following users thanked this post: newbrain

Offline Saskia

  • Super Contributor
  • ***
  • Posts: 2893
  • Country: de
  • you unlock this door with the key of imagination
Re: The worst programming language ever
« Reply #35 on: November 22, 2021, 08:17:30 am »
Mind you, it has been in the late 90s that I wrote that program. It replaced a pretty shitty shell script that took about an hour to run with a small script setting a couple of variables and calling make with the corresponding target. In those target definitions sed and awk took values from the calling shell script to define the targets on the fly by modifying the definitions during runtime and adapting file names and path names during execution. Execution time dropped by about 95 percent. I was happy, but the code would have one the obfuscated contest back then.
Oh well. The job that came after that one led me to a 3 letter company where I did software support for those folks in Poughkeepsie and Austin. Like debugging crash dumps of their power based ?IX machines and HA / parallel nodes.
Enjoyed it back then. Should not have left. Oh well.
 


Share me

Digg  Facebook  SlashDot  Delicious  Technorati  Twitter  Google  Yahoo
Smf

 

- - -
-->