# Mojo's impact on Numba

**URL:** <https://numba.discourse.group/t/mojos-impact-on-numba/1943>\
**Category:** Development\
**Created:** [May 16, 2023, 3:34pm UTC](https://numba.discourse.group/t/mojos-impact-on-numba/1943 "2023-05-16T15:34:39Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![sseibert](https://yyz2.discourse-cdn.com/free1/user_avatar/numba.discourse.group/sseibert/32/744_2.png) [@sseibert](https://numba.discourse.group/u/sseibert)\
**Post date:** [September 1, 2023, 9:02pm UTC](https://numba.discourse.group/t/mojos-impact-on-numba/1943/6 "2023-09-01T21:02:18Z")

</div>

Hi, apologies to revive this thread, but I have now posted a longer blog post on this topic that I think helps frame the comparison and give some thoughts on the relation the two projects could have:

> [@Numba / Mojo blog post](https://numba.discourse.group/t/numba-mojo-blog-post/2101):
>
> Hi all, This has sat in my backlog for a while, but the recent announcement of a new investment round in Modular.ai (the creators of Mojo) prompted to finish off a blog post over at the Anaconda Engineering Blog talking about Numba, Mojo, and generally how I think about the goals when compiling Python: If you have any questions, feel free to ask them here!

---

_[View the full topic](https://numba.discourse.group/t/mojos-impact-on-numba/1943)._