It would be cool if they'd put some resource into Pypy as well. Feels like that project is such a great achievement, and with just a bit more resource it would've been an amazing alternative. As it is, it takes a long time to get the new language features out, which always hamstrings it a little.
There's a limited number of volunteers with the experience to improve (C)Python, though, so the resources are better spent on improving the CPython implementation to such a point where PyPy is no longer necessary.
I believe both Google and Dropbox had a lot of Python code powering their products that they wanted to make faster. I don't think Microsoft has many large 1st party uses of Python. I think they're investing in it largely to gain developer mind-share.
So for Google and Dropbox "use another language" was an option, for Microsoft it's not.
Because if you want full ecosystem compatibility with as much performance as you can squeeze given that constraint, it makes more sense to start with the constraint satisfied rather than try to work toward it.
> Oh I think NIH syndrome.
Neither CPython nor PyPy was invented at Microsoft.
See: HHVM and PHP. HHVM is what lit the fire under the PHP team's collective butts to improve perf, and now most just run the mainline PHP interpreter (well, they did years ago when all this happened and I was still doing PHP)
I think that's because when new codebases are written, pypy isn't on the latest version of the Python spec, so people choose CPython. If it got a little more support it could get to parity or n-1, and far more projects would start with it and stick with it.
I don't use it myself, I just see the relatively small difference in investment it would be between a great project that's slightly languishing in obscurity despite incredible talent and effort, and a genuine full alternative to CPython.