
Hi, Brendan, In another post I said we considered making this open source, but our approach is new and unique and we don't think there is a rich volunteer community with the skills to translate Python directly to assembly language. I also talked about the unfortunate funding problems for open source projects -- including Python.org -- referring to Victor's PyCon presentation in 2019. It scared us about relying on open source funding to keep the project going without any real volunteer community. We plan to donate 5-10% of revenues to Python.org because we are very concerned about Python.org's funding problems, but we haven't said that on our site because it could sound presumptuous, if not arrogant, for a project just going into beta. The revenue sharing is similar to what we saw with JetBrains, where they recently shared 5% of revenue with Python.org for a 30-day period on sales of PyCharm. You asked why we posted this here for a product that is not open source. We wanted developer feedback, and so far we have gotten very useful feedback. We also wanted to see how it would be received by advanced Python developers. Your suggesting of incorporating it into CPython is very intriguing. We are open to all suggestions. Most the comments asked me to distinguish PysoniQ from the several available open source projects. I hope I have succeeded in answering those questions. There is a general implication that these are extravagant claims, but this project grew out of a previous project with APL translated directly to assembly, that involved more than 30,000 hours of development and testing. We never released it publicly because APL has a very small base. Regards, Mark