|
|
|
|
|
by Kednicma
2174 days ago
|
|
I like the bit at the end about studying the classics in Latin and Greek. It helps me see that "language" is not quite the right word for programming systems, and that this wrong word choice has led to writers falsely thinking that learning to program is like learning a second language. But a language is tied to its execution context and semantics. This leads to either dividing up languages into "natlangs" and "conlangs" depending on usage patterns and style, or to studying programming solely from the systems perspective and ignoring linguistics altogether. I wonder how things would have been different had we, as a community, rejected this terminology and stance. What if, even further, we had rejected the idea that computing can be made "simple" or "intuitive" or "mainstream", and instead forced folks to learn programming to APIs in order to even use computers. |
|
There's no justification for it. Maybe 20% of the population - at best - is even capable of that kind of programming. [1] Most people simply don't do symbolic abstraction at that level, and forcing them to try would create resentment, not literacy.
And "conlangs" are indeed different to "natlangs." There's definitely a case to be made for teaching everyone at least one extra language. But the kind of abstract thinking required for conlangs is adequately covered by basic STEM.
There might be a case for some very basic experience with programming in schools. But expecting the entire population to be able to do it at a professional level makes no more sense than expecting the entire population to have the same skills as qualified doctors, lawyers, architects, or pilots.
[1] There are fewer than 30 million developers globally, out of a population of nearly 8 billion.