2 ms·
Paul Graham is completely mistaken in that essay. You can't rank languages on a single one-dimensional axis labeled "power". Why? Start by asking the questio
by AnimalMuppet 4y ago
Paul Graham is completely mistaken in that essay.
You can't rank languages on a single one-dimensional axis labeled "power". Why? Start by asking the question, "Power to do what?" Well, duh, to write programs. "What programs?" Well, just general programs.
But I've never written a general program in my life. I've written a bunch of specific ones, though. What I care about is power to write this program. (Why do I care about how good a language is at writing programs that I'm not trying to write?)
There are a bunch of things that go into how good a language is at writing a specific program. Syntax. Libraries. Ecosystem. Availability of programmers who know the language. Maintainability. (If you think languages don't differ in terms of maintainability of programs written in them, work in COBOL for a while.) I should look at the language, and look at what I need to do to be able to write the program, and pick the language that, all things considered, will make it the easiest to write that program. The best language is going to vary from program to program.
And the reason it varies has nothing to do with the "Blub Paradox" or because we're too stupid to understand how wonderful some magical language is, either Lisp or Smalltalk.