# Community perspectives on the JIT: experiences, expectations, and concerns

**URL:** <https://discuss.python.org/t/community-perspectives-on-the-jit-experiences-expectations-and-concerns/107737>\
**Category:** Core Development\
**Created:** [June 11, 2026, 10:34pm UTC](https://discuss.python.org/t/community-perspectives-on-the-jit-experiences-expectations-and-concerns/107737 "2026-06-11T22:34:43Z")\
**Posts on this page:** 1\
**Showing post:** 69

<div class="post-metadata">

**Author:** ![cdimauro](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/cdimauro/32/36066_2.png) [@cdimauro](https://discuss.python.org/u/cdimauro)\
**Post date:** [July 1, 2026, 5:00am UTC](https://discuss.python.org/t/community-perspectives-on-the-jit-experiences-expectations-and-concerns/107737/69 "2026-07-01T05:00:34Z")

</div>

> [@jacopoabramo](#):
>
> Or we could simply leverage `typing.Protocol` and approach in the same manner as rust does with traits (which, as a concept, is close to how mypyc interprets this). So instead we give up entirely on inheritance and embrace composition.

I prefer to keep them separate and decide by myself which one to use as per my convenience/vision on how I want to model the world (usually, to me `is` → inheritance and `has` → composition, but I might take different decisions strictly depending on the specific use-case).

---

_[View the full topic](https://discuss.python.org/t/community-perspectives-on-the-jit-experiences-expectations-and-concerns/107737)._