>It's not as popular therefore it's not as good. Your logic is definitely valid!
And your logic is definitely faulty. I've never used the word "good"
What I said is "more productive" (what the author claims) can only be measured in actual PRODUCTION.
That is, the important thing is not:
(a) "If I were to use X framework/language, how productive would I be over Y framework/language?",
but:
(b) "In an actual empirical observation, what framework/language is actually responsible for the largest volume of production?"
The author talks about (a), and advocates Haskell. But that is not an empirical, scientific, measurable observation, it's just his personal opinions, feelings and anecdotes. Only (b) gives an actual overall metric of the productivity of two frameworks/languages combos.
Even having the same person doing the exact same project with both X and Y framework/languages and comparing the speed with which each was done, would tell us very little. Maybe someone he was more comfortable with one or the other, maybe that particular project fitted especially X over Y, maybe it didn't need to communicate with legacy stuff with neither X nor Y do well, etc.
The only way to tell what generally was for production for the majority of people, is to, DUH, see what the majority of people have used for their productions.
And your logic is definitely faulty. I've never used the word "good"
What I said is "more productive" (what the author claims) can only be measured in actual PRODUCTION.
That is, the important thing is not:
(a) "If I were to use X framework/language, how productive would I be over Y framework/language?",
but:
(b) "In an actual empirical observation, what framework/language is actually responsible for the largest volume of production?"
The author talks about (a), and advocates Haskell. But that is not an empirical, scientific, measurable observation, it's just his personal opinions, feelings and anecdotes. Only (b) gives an actual overall metric of the productivity of two frameworks/languages combos.
Even having the same person doing the exact same project with both X and Y framework/languages and comparing the speed with which each was done, would tell us very little. Maybe someone he was more comfortable with one or the other, maybe that particular project fitted especially X over Y, maybe it didn't need to communicate with legacy stuff with neither X nor Y do well, etc.
The only way to tell what generally was for production for the majority of people, is to, DUH, see what the majority of people have used for their productions.