Excellent discussion of verbosity (many keywords), orthogonality (scalar vs record expressions, calling conversations) and semantics (bizarre equality for NULL) in database query languages, focusing on SQL: https://edgedb.com/blog/we-can-do-better-than-sql/
(Uses 'design by implementation' as derogatory!)
miniblog.
Related Posts
I'm changing method definition syntax in my language:
// old
fun (this: Int) inc(): Int { this + 1 }
// new
method inc(this: Int): Int { this + 1 }
The original syntax was inspired by Go, but the new syntax is more grep-friendly and perhaps more readable. Not sure about the verbosity though. Thoughts?
I feel like increasing visibility of a function/type should require more verbosity. I don't know of any PL that follows this design principle for >2 levels though.
Ordered by verbosity:
public, private, protected
, pub, pub(crate)
Has any PL solved this?
Discussing different ways of passing values through nested React components: https://blog.logrocket.com/mitigating-prop-drilling-with-react-and-typescript/
In addition to showing examples of each, they count lines of code as a rough verbosity measure!