Because it's a niche language with a very small ecosystem.

Whereas Python has tons of libraries, millions of programmers, tons of support, tons of documentation and books, and billions of lines of existing codebases...

> Because it's a niche language with a very small ecosystem.

Python was like that once, too. Now we have the necessary experience to understand what are crucial aspects of the language that are missing but are extremely difficult to change post-factum, such as removing the GIL. Nim has no such constraints, and while building the ecosystem takes time, I have no doubts it will progress smoothly as Nim is such a pleasure to use. Even for such a young language I feel we're already in a good shape: https://github.com/nim-lang/Nim/wiki/Curated-Packages.

Nim is actually really good and a pleasure to use. But Python, sadly, dominates the market space and there's a lot of existing code that would get a minor boost. And as Python plans to be 5x faster in a few years, so it's part of that process.

Nim doesn't make existing python vide bases faster.

Also, do you really think the Python team should just give up on performance just because faster languages exist?

Should Tesla stop building cars as soon as someone builds a faster car than them?

Actually it is possible, Nim compiles to C and is a viable alternative to CPython.

nimpy https://github.com/yglukhov/nimpy PyGotham talk: https://www.youtube.com/watch?v=IVgNVJdizHg another blog post: https://robert-mcdermott.gitlab.io/posts/speeding-up-python-...

This doesn't make existing python code bases faster. You have to rewrite in nim.

Yeah (rewrite) just the hotpaths like you would with Cython. Also there is https://github.com/Pebaz/Nimporter which makes it easier.

I believe OP means new code bases; rewriting the existing ones obviously makes sense only in specific cases where performance is a key factor.

Go to the Nim forums and check out some posts from people who wish Nim was more like Python. In the Nim tutorials, they appear to be closely related, so when new users encounter Nim, a port from Python code to Nim seems reasonable. If you post anything like this on the forums, get ready for some hate.

Nim wants to be its own thing, and posters are quick to point out that Nim isn't Python, never was intended to be, and never will be. That's what the DFL wants, which is fine. But IMO, creating a language that is closely-related to Python, arguably one of the world's most popular languages, and allows / encourages porting large Python codebases, seems like a pretty worth goal. Now that Nim has already made a lot of decisions to make that difficult, it can't pivot to that goal without breaking all the existing Nim code. Too bad: seems like a big opportunity lost to me.

> creating a language that is closely-related to Python, arguably one of the world's most popular languages, and allows / encourages porting large Python codebases, seems like a pretty worth goal.

well they do state "copying bad design is not good design" in the main page. Actually porting Python code to Nim is not that difficult especially when people care enough to create pages like: https://github.com/nim-lang/Nim/wiki/Nim-for-Python-Programm...