The sophistication around developing smart contracts in Solidity from tooling to security practises is far too high for any contract to compete against at this point. The biggest data point I see for this being true is Uniswap v1 having been written in Vyper only in v2 to move back to Solidity. OpenZeppelin has even gone as far as to say that they strongly advise against using Vyper to write smart contracts.

What this means for any chain (including Ethereum) is that Solidity is here to stay until another language can gain critical mass with battle tested applications going live and experiencing many millions of dollars in losses to gain critical learnings. Sure a language doesn't cause exploits, only implementers. However, developers and community don't have the same understanding of a language as the developers who made it. Blog posts, tutorials and extensive documentation are required to create a shared understanding of creating secure, production grade smart contracts.

Not only is Solidity an issue, but the entire ecosystem of creating smart contracts around it. For example, the following is required for any production grade contracts to be made:

* Smart contracts written in a language with plenty of support and community questions

* Contracts that compile into a type-safe language to ensure smooth integrations

* Test suite that ensures test-driven development can be performed

* CI/CD checks such as code coverage, static analysis & linting

* Plenty of free node providers to deploy contracts with no hassles