3 ms·

I am very confused by this article. When we use the word 'program' in computing, we pretty much always mean 'a program for a (previously or implicitly defined)

by qsort 5y ago

I am very confused by this article. When we use the word 'program' in computing, we pretty much always mean 'a program for a (previously or implicitly defined) computational model', I don't see in what sense this is comparable to 'program clocks', which are basically timers/alarm clocks, if I understand that paragraph correctly. Similarly, when we say 'code' we mean 'textual representation of the concrete syntax', clearly distinct from 'code' as in 'morse code', which we would also call 'encoding'. > This strengthens a computing discipline where one often cares more about formalism than about actual programming This is (perhaps) a (somewhat) fair criticism of (parts of) computer science as an academic field of study, but I don't get how the pieces fit toghether.

kragen 5y ago
> When we use the word 'program' in computing, we pretty much always mean 'a program for a (previously or implicitly defined) computational model', I don't see in what sense this is comparable to 'program clocks', which are basically timers/alarm clocks, if I understand that paragraph correctly. It seems that a "program clock" was a clock that you could, more or less in the modern sense, program; you could put a plan into it, and then it would carry out the plan. Like those electromechanical outlet timers that you can set to turn on your floor lamps at certain times of day when you're not home. The "program" for those is the little slidy things around the dial that define when to turn the light on or off. In the same way, a computer program is a plan that you can put into a computer, thus programming the computer to carry out the program. That concept isn't just comparable to that of the program you put into a program clock; it's identical, though there are some things the program clock can't do.
AnimalMuppet 5y ago
> Similarly, when we say 'code' we mean 'textual representation of the concrete syntax', clearly distinct from 'code' as in 'morse code', which we would also call 'encoding'. You're thinking in modern terms. When you had to program in octal, "encoding" was exactly what you were doing. Assemblers and, later, compilers made that less true, but originally that was in fact the meaning.
leetcrew 5y ago
it's worth teasing apart where words come from. the term "dynamic programming" does not make a lot of sense until you understand the historical context.
- taeric 5y ago
  Even knowing the context, it still doesn't really add anything to my understanding. :( Is a case of a name that is intentionally not useful to describe what it named. So frustrating.

by qsort 5y ago

kragen 5y ago

> When we use the word 'program' in computing, we pretty much always mean 'a program for a (previously or implicitly defined) computational model', I don't see in what sense this is comparable to 'program clocks', which are basically timers/alarm clocks, if I understand that paragraph correctly. It seems that a "program clock" was a clock that you could, more or less in the modern sense, program; you could put a plan into it, and then it would carry out the plan. Like those electromechanical outlet timers that you can set to turn on your floor lamps at certain times of day when you're not home. The "program" for those is the little slidy things around the dial that define when to turn the light on or off. In the same way, a computer program is a plan that you can put into a computer, thus programming the computer to carry out the program. That concept isn't just comparable to that of the program you put into a program clock; it's identical, though there are some things the program clock can't do.

AnimalMuppet 5y ago

> Similarly, when we say 'code' we mean 'textual representation of the concrete syntax', clearly distinct from 'code' as in 'morse code', which we would also call 'encoding'. You're thinking in modern terms. When you had to program in octal, "encoding" was exactly what you were doing. Assemblers and, later, compilers made that less true, but originally that was in fact the meaning.

leetcrew 5y ago

it's worth teasing apart where words come from. the term "dynamic programming" does not make a lot of sense until you understand the historical context.

taeric 5y ago
Even knowing the context, it still doesn't really add anything to my understanding. :( Is a case of a name that is intentionally not useful to describe what it named. So frustrating.