For clarity, I'm talking mainly about SimCorp[0], which is a user of Dyalog APL, not kdb. The core of Dimension uses APL (with many other parts in C#), and ther

For clarity, I'm talking mainly about SimCorp[0], which is a user of Dyalog APL, not kdb. The core of Dimension uses APL (with many other parts in C#), and there's a separate APL product bought with APL Italiana as well. They employ hundreds of APL programmers, preferring to hire math and physics majors out of college because they're easier to teach. Yes, SimCorp probably wouldn't start with APL today, and I wouldn't give it a second thought either if I were trying to start a big business. I pointed to the large codebases because they're easier to quantify, but I'm sure there are millions of lines written by hobbyist developers. I know you're not trying to flame, but what you've given us so far is a false claim that nobody writes code in APL, and a bare assertion that APL is a bad way to program. On that note, you're trying to say a language you've never used doesn't allow for "abstraction" or "a focus on readability", which I think is dead wrong. All of which is at best tangentially relevant to Iverson's claim in the paper (not APL's founding document, by the way; that would be A Programming Language) that APL's notation is a way to enhance your thinking. APL has good and bad aspects, and there's a lot to discuss, but can it please be a discussion instead of these careless remarks? [0] https://en.wikipedia.org/wiki/SimCorp https://en.wikipedia.org/wiki/SimCorp