I'm not sure I agree with the author's conclusion. While python was never a great language for large codebases and it thrived because people with little development knowledge could get going pretty easily, a large part of its current appeal is the profusion of great specialized libraries which you would have to code yourself in other languages.
I suspect vibe coding will not be a good fit for writing these libraries, because they require knowledge and precision which the typical vibe coding use probably doesn't show, or the willingness to spend time on the topic which is also typically not what drives people to vibe coding.
So my conclusion would be that vibe coding drives the industry to solidify around already well-established ecosystem, since less of the people producing code will have the time, knowledge and/or will to build that ecosystem in newer languages. Whether that drive is strong enough to be noticable is another question.
Then again, LLMs are well-suited to translate stuff, a relatively grunt work kind of task, so porting libs to your ecosystem of choice is a lot more feasible now.
Perhaps there is a future where individuals can translate large numbers of libraries, and instead of manually porting future improvements of the original versions to the copies, just rerun the translation as needed.
Yup, I recently started doing more development in Nim. I love the language, but the user community is (currently) small, which means the ecosystem of libraries available isn't as big. But LLMs are a massive equalizer here and has made it a lot easier for me to get things done with Nim.