<story><title>Pony Programming Language</title><url>https://github.com/ponylang/ponyc</url></story><parent_chain></parent_chain><comment><author>CobrastanJorji</author><text>I want to thank whoever wrote the &amp;quot;Why Not To Use Pony&amp;quot; bullet points. They&amp;#x27;re quite honest and helpful. Most of these sorts of pages are 110% &amp;quot;rah rah our language is the best for every possible situation, which makes it hard to figure out how to evaluate them. For me personally, this has seemed worst with database products. No matter what the database&amp;#x27;s actual pros and cons are, their project pages will swear that they are the best at every possible scenario that might involve data.</text></comment>
<story><title>Pony Programming Language</title><url>https://github.com/ponylang/ponyc</url></story><parent_chain></parent_chain><comment><author>wiremine</author><text>A previous conversation: &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;news.ycombinator.com&amp;#x2F;item?id=17195580&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;news.ycombinator.com&amp;#x2F;item?id=17195580&lt;/a&gt;&lt;p&gt;On a sort-of-related topic: I&amp;#x27;ve been checking out the Inko programming language, which has some similar goals&amp;#x2F;ideals as Pony:&lt;p&gt;&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;inko-lang.org&amp;#x2F;&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;inko-lang.org&amp;#x2F;&lt;/a&gt;&lt;p&gt;Inko lists Erlang and Pony as inspiration for its concurrency model:&lt;p&gt;&amp;quot;Inko uses lightweight processes for concurrency, and its concurrency model is inspired by Erlang and Pony. Processes are isolated from each other and communicate by sending messages. Processes and messages are defined as classes and methods, and the compiler type-checks these to ensure correctness.&amp;quot;</text></comment>