Expressivity and verbosity are two not entirely orthogonal axes. For example, both Haskell and Lisps are thought to be highly expressive (in the meaning that constructs not available in the language can be created and used as if they are “native”), but Haskell is arguably less verbose due to being able to express many things without parens, use (often strange and unreadable) symbols, etc.
Patterns are twofold. Some do come from lack of expressivity, eg Visitor pattern, which is equivalent to pattern matching in FP languages, but many others are rather architectural ones, that are not made obsolete by any other language.
Not having properties is absolutely not an expressivity problem but a (questionable) verbosity one, because it is trivial to accomplish their goal. On the other hand adding generics to C is simply not really possible (or some ugly satanic thing with macros at most), it is an expressivity problem. Java’s generics may be considered a verbosity problem due to not as strong type inference as eg Haskell.
Expressivity and verbosity are two not entirely orthogonal axes.
By this logic any Turing-complete language with code generation is absolutely expressive. If it would be the convenient way of using PLs, than we should end up with super simple macro assembly with everything added as generated patterns on top of it, or at least with lisp.
On the other hand adding generics to C is simply not really possible (or some ugly satanic thing with macros at most)
Because parametric polymorphism is harder to implement with code generation than immutable records, but still possible. Both cases are still examples of lack of expressive power, just of different severity.
1
u/Muoniurn Apr 21 '21
Expressivity and verbosity are two not entirely orthogonal axes. For example, both Haskell and Lisps are thought to be highly expressive (in the meaning that constructs not available in the language can be created and used as if they are “native”), but Haskell is arguably less verbose due to being able to express many things without parens, use (often strange and unreadable) symbols, etc.
Patterns are twofold. Some do come from lack of expressivity, eg Visitor pattern, which is equivalent to pattern matching in FP languages, but many others are rather architectural ones, that are not made obsolete by any other language.
Not having properties is absolutely not an expressivity problem but a (questionable) verbosity one, because it is trivial to accomplish their goal. On the other hand adding generics to C is simply not really possible (or some ugly satanic thing with macros at most), it is an expressivity problem. Java’s generics may be considered a verbosity problem due to not as strong type inference as eg Haskell.