It has been said that non-programmers used to catch on to APL quite quickly back in the day. Faster than regular programming languages in fact. The designers, Ken Iverson, didn't even design the language to be run on computers but rather as a mathematical notation.
Someone else mentioned Excel, and that is an example of data-oriented programming. It actually hides the code and displays the data, which is why most programmers hate it. It's not the data that is important when doing development, but the code.
Array oriented languages like APL and R allows you to work with data like Excel, but you work with the code, not the numbers. I'd argue that once you learn more about programming, one tends to want to work with the code rather than just looking at data.
I've observed the opposite trend. The more senior people get the more they care about the data and less about the code.
Programming = Datastructures + Algorithms
But it's the Data-structures/-models that dictate the algorithms and it's the domain and data therein that dictates the model.
Most companies could survive their code being lost. None would survive loosing all their customer data.
Functional programming is all about data, react is about data, machine learning is about data, google and facebook are about data.
Code is an incidental means to an end, in 90% of all cases, except flight software and games maybe, but even there the trend is towards data driven ECS-Systems and "collect all data for a timestep, and execute your flight control program to compute all actuator outputs in one go"-approaches.
And observability is one of THE hot topics in the biz right now.
Thompson and Ritchie also said their secretaries happily wrote troff.
Do people get pampered too much today or are we severely underestimating them?
Also, there was a major difference between what the secretaries would have been using before troff and their experience with troff. In particular, at that time, they were probably using typewriters. A digital workflow would have been a massive improvement in experience. Need multiple copies? No more carbon copies or retyping, now it just comes off the printer (which may still use a carbon copy, but at least you don't have to retype it). Need to adjust something? At least for future printouts it's just changing the file, and maybe using whiteout and handwriting the correction in a few printouts. Want to reflow the entire page? On a typewriter you start over, with troff you edit.
Today, people have Word and Google Docs, why do they need troff/Markdown/TeX/LaTeX/Asciidoc/org-mode/etc.?
The experience, for the user, is not as qualitatively different as those secretaries would have experienced at the time. Not just secretaries, my parents (a pilot and an engineer) took to computers in the 1970s (in college)/1980s (work, later home) for the same reason, it was a better experience than using typewriters and hand calculating things (even with a calculator).
Because what they write has structure and they don't want to be distracted by the looks.
Regarding your "don't want to be distracted", Word has had an outline mode since at least 1995 (first time I used Word). Not sure about Google Docs, but it's a perfectly fine distraction free writing environment. So that's not even a selling point for users of Word.
I just don't object to anything but that one question.
> Word has had an outline mode since at least 1995
I haven't had Word for years so I can't check it out, but if you take WYSIWYG out of a WYSIWYG editor, what is left? Why would I use it instead of other tools you listed? I have used some of them.
This is still true today. I used to run a program for kids where they coded with robots. We used C for a while and we spent the whole time teaching C, never really getting to cool robot activities. Then we switched to Matlab, and it was like night and day. They took to Matlab so quickly, and I think you are right that the array nature of the language is the main reason. Others include the ubiquitous table datatype, and a REPL interface.
R is ugly because it encourages users to use it wrong. For loops are slow as a snail, but are what everybody uses and teaches, while the proper/fast way to wrangle data, with higher order functions like map, is hidden behind idiosyncratic names and obscure APIs.
Even the creator of R considered making it a language instead of the scheme library that it started iut as, as a mistake.
Instadeq: A Live Programming Environment for End User Data Analysis and Visualization
Video: https://www.youtube.com/watch?v=mTEkYqnGICE Slides: https://marianoguerra.github.io/presentations/2021-live/
There is no world in which listing the columns before the tables in a SELECT statement is a good idea. It makes intellisense/autocomplete awkward.
These probably shouldn’t matter but did for me. FWIW the statistical offering was fantastic.
I'm sure it is poorly designed from a computer science perspective, but there is no programming language out there which makes it so easy to run any model under the sun as does R.
In Python’s case, the language isn’t bad, but the implementation is horrible for performance. It sits on the back of lots of fast C/Fortran/whatever code, and polished the (relative) turd a lot, making the end result quite usable, but the “sitting on top of part” also makes it hard to improve the performance of the implementation.
For both R and python the end result is good, but they still are local optima in the space of what is possible.
The good: Excel, Dataflow Diagrams (commonly found in game, music and arts), SQL, Declarative Dataflow Paradigms in general. Mutablity is counterintuitively counterintuitive if you don't have a model of the underlying execution system.
The weird: Prolog, APL, languages done by mathematicians and logicians
The ugly: SPSS, R, two languages done by statisticians, and they are absolutely abhorrent, and often missused.
If we reinvented programming today my guess is that it would be a lot less text driven and a lot more data oriented.