Why would it be hostile? There&#x27;s tons of Python2 users out there like me that need support and a secure path forward with Python, and my code.<p>PyPy didn&#x27;t create that situation, CPython did. They&#x27;re just filling a market need. It may be opportunistic, but it&#x27;s hardly hostile. If anything was hostile it was CPython3, but I&#x27;d say neither would be &quot;hostile&quot; moves.<p>Everyone should always act in their own best interests. Especially users like myself. The CPython team did what they felt was in theirs. I do what I feel is mine. PyPy should do the same, not be fearful of some toxic, &quot;hostile&quot; accusation.<p>The godsend is that I don&#x27;t have to worry about CPU performance being a limiting factor at all. That&#x27;s a big deal and reduces my hardware needs to do the same amount of work. My VPS is hardly overpowered, and I like it that way because it&#x27;s cheap for my projects. :) CPython only exacerbates hardware issues.<p>It&#x27;s very nice to have a simple interpreter to fall back on, but at this point in time I think most dynamic languages need to be on a JIT like PyPy. It&#x27;s just too good and I can&#x27;t wait for the STM branch to be merged into PyPy4. No more GIL for those of us using it.