3 ms·
That same generation of programmers also moved us out of the GOTO hell that they existed in with more reasonable structured languages. There's a reason, and it'
by Jtsummers 11y ago
That same generation of programmers also moved us out of the GOTO hell that they existed in with more reasonable structured languages. There's a reason, and it's not just coincidence, that old school Fortran and BASIC and assembler written in an unstructured manner is difficult to maintain and reason about, while software written in more structured language is easier to maintain and reason about.
This is what Dijkstra was commenting about. It's related to his "Go to statement considered harmful" (1968) paper and his text (with Hoare and Dahl) Structured Programming (1972).
EDIT: I was looking for something like this.
https://en.wikipedia.org/wiki/Dartmouth_BASIC https://en.wikipedia.org/wiki/Dartmouth_BASIC
Version 6 saw the introduction of separately compilable
procedures with parameters. In 1976, Steve Garland added
structured programming features to create Dartmouth SBASIC,
a precompiler which produced version 6 output (and which
formed the basis of ANSI BASIC).
Structured programming was introduced into at least this version of BASIC after Dijkstra's statement about BASIC causing brain damage.
- Turing_Machine 11y agoYou are missing my point, I think. There is no reason why "language suitable for building gigantic, uber-complex, mission-critical systems" and "language suitable for fooling around with as a beginner" should be the same, and many reasons why they shouldn't.
- Jtsummers 11y agoI never said they should. But languages like the historic BASIC created a set of habits and ideas that had to be unlearned to build reliable, scalable software. Your example of JavaScript as a modern BASIC is a different language. It provides all the structured programming ideas that Dijkstra wanted. Where it fails (failed?) is in its concurrency mechanism favoring a version of callback hell and its weak type system. Those are much easier to overcome than first learning to code by interleaving code blocks and using gotos rather than subroutines, while loops and the like.