<story><title>Dada, an experimental new programming language</title><url>https://dada-lang.org/</url></story><parent_chain><item><author>yamrzou</author><text>Their Hello, Dada! example:&lt;p&gt;print(&amp;quot;...&amp;quot;).await&lt;p&gt;I&amp;#x27;m coming from Python, and I can&amp;#x27;t help but ask: If my goal as a programmer is to simply print to the console, why should I care about the await? This already starts with a non zero complexity and some cognitive load, like the `public static void main` from Java.</text></item></parent_chain><comment><author>wtetzner</author><text>&amp;gt; If my goal as a programmer is to simply print to the console, why should I add care about the await?&lt;p&gt;Because that isn&amp;#x27;t ever anyone&amp;#x27;s actual goal? Optimizing a language design for &amp;quot;Hello World&amp;quot; doesn&amp;#x27;t seem like a particularly useful decision.</text></comment>
<story><title>Dada, an experimental new programming language</title><url>https://dada-lang.org/</url></story><parent_chain><item><author>yamrzou</author><text>Their Hello, Dada! example:&lt;p&gt;print(&amp;quot;...&amp;quot;).await&lt;p&gt;I&amp;#x27;m coming from Python, and I can&amp;#x27;t help but ask: If my goal as a programmer is to simply print to the console, why should I care about the await? This already starts with a non zero complexity and some cognitive load, like the `public static void main` from Java.</text></item></parent_chain><comment><author>baq</author><text>I&amp;#x27;d say you want something like &amp;#x27;debug_msg()&amp;#x27; for this.&lt;p&gt;&amp;#x27;print()&amp;#x27; should be async because it does IO. In the real world most likely you&amp;#x27;d see the output once you yield.</text></comment>