<story><title>Towards a new SymPy</title><url>https://oscarbenjamin.github.io/blog/czi/post1.html</url></story><parent_chain></parent_chain><comment><author>carapace</author><text>Part II made the front page yesterday: &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;news.ycombinator.com&amp;#x2F;item?id=37426080&quot;&gt;https:&amp;#x2F;&amp;#x2F;news.ycombinator.com&amp;#x2F;item?id=37426080&lt;/a&gt;&lt;p&gt;A comment there makes what I think is a very good point about &amp;quot;the lack of consolidation of computer algebra efforts&amp;quot;: &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;news.ycombinator.com&amp;#x2F;item?id=37430437&quot;&gt;https:&amp;#x2F;&amp;#x2F;news.ycombinator.com&amp;#x2F;item?id=37430437&lt;/a&gt;&lt;p&gt;I don&amp;#x27;t know what might drive or foster such consolidation.  Maybe Category Theory?  Bridging syntax?</text></comment>
<story><title>Towards a new SymPy</title><url>https://oscarbenjamin.github.io/blog/czi/post1.html</url></story><parent_chain></parent_chain><comment><author>mathisfun123</author><text>The unfortunate thing is that core CAS functionality (and performance) should be based on a SAT&amp;#x2F;SMT engine to discover the rewrite rules and it goes without saying (but I&amp;#x27;ll say it anyway) implementing that is &amp;quot;hard&amp;quot;. Naively (i.e., I haven&amp;#x27;t &lt;i&gt;really&lt;/i&gt; thought through it), I think sympy should be built on top of z3 or cvc5 or at least very tighly integrated (e.g., support as a backend). And (again naively) I think until such time, sympy will remain a toy.&lt;p&gt;I will say though that symengine is a great project and congrats to that guy for pulling it off under the constraints of a phd.</text></comment>