4 ms·
There are common arguments the other way. Do you remember how hard it was to memorize, or at least become familiar with, all of the API function names? Or with
by eesmith 6y ago
There are common arguments the other way.
Do you remember how hard it was to memorize, or at least become familiar with, all of the API function names? Or with various language syntax, like generator comprehensions and decorators? Over the years, and with practice, it's much easier to remember the details. The same is true with the terse notations of the APL-like languages - once you learn them, they are not hard.
And there aren't all that many symbols. Some of what you see are composeable combinations of basic symbols.
Or, think of shorthand, which takes time to learn, but makes it possible to, for example, take dictation at a speed that longhand cannot manage. While I don't think most programming is limited by typing speed, I do think that for some sorts of exploratory research it is. For a related essay, see https://steve-yegge.blogspot.com/2008/09/programmings-dirtiest-little-secret.html https://steve-yegge.blogspot.com/2008/09/programmings-dirtie... .
Finally, APL fans will (correctly, IMO) point out that (in)visibility is part of what makes something hard. That is, code which fits on the screen is easier to read than code which flows over several pages. Thus, the effort of learning a more concise language may pay off in the long-run.
(Note that I don't work with numeric arrays and have little experience even with NumPy - I've just read about this debate often.)