Hacker News Reader

I neither want to deny or confirm this but if love to see a more in depth analysis of the idea.

Why? Is it because of the "fine grained control" part? Because it breaks the neat abstraction?

Expressiveness is too powerful. I have to understand what the author was thinking. What you typically want is composition. With composition, you have to understand what the author is doing.

Painting with acrylics vs Lego.

fair point, expressiveness shifts idioms toward "single man private jokes"

A point I just realize the value.

But you could just have expressiveness through composition then?

It's basically the same reason Go was created: not many advanced features, lack of abstraction power, leading to highly predictable codebases so that companies can easily onboard new software engineers.

This was probably the theory behind their decisions. While I agree that the lack of expressiveness might discourage some incidental complexity, for example premature or unecessary abstractions, the inherent complexity of a problem will remain. Removing expressive power, in general, will lead to ad-hoc and cumbersome workarounds. For example, look what the Kubenetes codebase had to do to work around the lack of generics: https://medium.com/@arschles/go-experience-report-generics-i...

Reply on news.ycombinator.com