I wrote a blog post making a similar point with Clojure as an example: https://vvvvalvalval.github.io/posts/2018-01-06-so-yeah-about-clojures-syntax.html https:

I wrote a blog post making a similar point with Clojure as an example: https://vvvvalvalval.github.io/posts/2018-01-06-so-yeah-about-clojures-syntax.html https://vvvvalvalval.github.io/posts/2018-01-06-so-yeah-abou... The core ideas are timeless really, but the examples might be a bit more relatable today. I'm reproducing the ToC here: 1. Does syntax matter? 2. The ingredients of Clojure's syntax 2.1 Data literals 2.2 Macros 3. Consequences 3.1 Verbosity is a solved problem 3.2 Separation of concerns: code layout ⊥ program structure 3.2.1 Example: the Builder Pattern 3.3 Code = Data = Data Viz 3.4 Tooling as libraries 3.5 An 'all-tracks' language: embedding paradigms 3.5.1 Example: Web UIs 3.6 Saner language stewardship 4. Summary