&gt; The more you want your code to be small, the more you&#x27;re gonna need a programming environment (language&#x2F;API&#x2F;runtime&#x2F;framework) doing things for you under the hood. And there&#x27;s nothing wrong about it!<p>Or have your code do one thing and only one thing, a single purpose, with clear, well defined interfaces and then compose things doing only one thing to a bigger thing that you can reason about more easily because the interfaces and processes are well-defined.<p>One thing I&#x27;ve seen too much of in my professional life is complex projects trying to do too much, with ill-defined roles and implicit, poorly documented interfaces.<p>Simplicity of a language works well as long as your projects are kept simple. You can build fairly complex solutions by composing multiple simple projects with well defined interfaces.<p>I think we agree that simplicity of a language works less well when the scope of a single project is too large and too arbitrarily defined.