<div dir="rtl"><div dir="ltr">Hey Guys,<br clear="all"></div><div dir="ltr"><br></div><div dir="ltr">The big data and machine learning world is dominated by Python, Scala an R. <br></div><div dir="ltr"><br></div><div dir="ltr">I'm a Swifter by heart, but not so much by tools of trait. </div><div dir="ltr"><br></div><div dir="ltr">I'd appreciate a constructive discussion on how that could be changed.</div><div dir="ltr"><br></div><div dir="ltr">While R is a non goal for obvious reasons, i'd argue that since both Scala and Python are general purpose languages, taking them head to head might be a low hanging fruit.</div><div dir="ltr"><br></div><div dir="ltr">To make the claim I'd like to reference to projects such as </div><div dir="ltr"><br></div><div dir="ltr"> - Hadoop, Spark, Hive are all huge eco-systems which are entirely JVM based.</div><div dir="ltr"> - Apache Parquet, a highly efficient column based storage format for big data analytics which was implemented in Java, and C++.</div><div dir="ltr"> - Apache Arrow, a physical memory spec that big data systems can use to allow zero transformations on data transferred between systems. Which (for obvious reasons) focused on JVM, to C interoperability.</div><div dir="ltr"><br></div><div dir="ltr">Python's Buffer Protocol which ensures it's predominance (for the time being) as a prime candidate for data science related projects <a href="https://jeffknupp.com/blog/2017/09/15/python-is-the-fastest-growing-programming-language-due-to-a-feature-youve-never-heard-of/" target="_blank">https://jeffknupp.com/blog/<wbr>2017/09/15/python-is-the-<wbr>fastest-growing-programming-<wbr>language-due-to-a-feature-<wbr>youve-never-heard-of/</a></div><div dir="ltr"><br></div><div dir="ltr">While Swift's Memory Ownership manifesto touches similar turf discussing copy on write and optimizing memory access overhead it IMHO takes a system level perspective targeting projects such as kernel code. I'd suggest that viewing the problem from an efficient CPU/GPU data crunching machine perspective might shade a different light on the requirements and use cases. </div><div dir="ltr"><br></div><div dir="ltr"><br></div><div dir="ltr">I'd be happy to learn more, and have a constructive discussion on the subject.</div><div dir="ltr"><br></div><div dir="ltr"><br></div><div dir="ltr">Thank you,</div><div dir="ltr">Max.</div><div dir="ltr"> </div><div dir="ltr"><br></div><div dir="ltr">-- <br></div><div class="m_6237153780122507907gmail_signature" dir="ltr"><div>puıɯ ʎɯ ɯoɹɟ ʇuǝs<br></div></div>
</div>