<story><title>Uiua: A minimal stack-based, array-based language</title><url>https://www.uiua.org/</url></story><parent_chain><item><author>kaikalii</author><text>Oh hey, I made this.
Cool to see it at the top of HN!</text></item></parent_chain><comment><author>fyzix</author><text>The arrows that iterate through the steps is great UX. I&amp;#x27;m new to both array and stack based programming and it was pretty intuitive.&lt;p&gt;How would I go about file i&amp;#x2F;o and parsing json? I have a data processing benchmark[1] that I&amp;#x27;d like to use this for.&lt;p&gt;[1] : &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;jinyus&amp;#x2F;related_post_gen&quot;&gt;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;jinyus&amp;#x2F;related_post_gen&lt;/a&gt;</text></comment>
<story><title>Uiua: A minimal stack-based, array-based language</title><url>https://www.uiua.org/</url></story><parent_chain><item><author>kaikalii</author><text>Oh hey, I made this.
Cool to see it at the top of HN!</text></item></parent_chain><comment><author>derefr</author><text>I want to suggest an alternative encoding&amp;#x2F;notation where instead of single (very nicely chosen) Unicode codepoints, the operators are single (perhaps less well-suited) printable ASCII characters. This would make the language into its own, human-authorable, bytecode!</text></comment>