⭐️ Something important but rarely discussed in the Ethereum ecosystem is happening: the most widely used smart contract language, Solidity, is about to "split" into two versions—Classic Solidity, which emphasizes stability, and Core Solidity, a complete overhaul that is still in the prototype stage. Both languages will be maintained by the Solidity team. They believe that the limitations of early design references have impacted Solidity's architecture, and nearly 10 years of evolution have introduced significant technical debt. Additionally, some syntax features (like generics) are missing, and trying to patch or add these features to the current system would be extremely risky. Since Solidity is a smart contract language, security/stability is more important than feature richness. That’s why they believe developing two languages simultaneously is the best approach. Core Solidity will be built from scratch, natively supporting new features, introducing a standard library, and establishing a new language specification. Currently, Solidity’s version is 0.8.30, and the upcoming 0.9 release will mark the first step in transitioning from Classic Solidity to Core Solidity. It won’t introduce major new features yet, but its primary goal is to remove deprecated functionality and address technical debt. The subsequent 0.10 version will remove more outdated elements, with some syntax evolving toward Core Solidity’s style. What does the community think about this? 1️⃣ Paradigm’s @gakonst believes that the current Solidity is "basically fine," and the top priority isn’t new syntax or language features but improving the compiler itself—specifically, how to boost compilation speed and gas optimization by 100x. He’s worried Solidity might repeat the ecosystem split that happened when Python 2 upgraded to Python 3. 2️⃣ Some developers have expressed concerns that maintaining two languages simultaneously will be extremely challenging, especially for third-party tooling. 3️⃣ On the forums, someone pointed out that one of the main complaints from the developer community is Solidity’s slow compilation speed. They asked how the design could improve compilation speed or adopt incremental compilation techniques. The Solidity team responded that they’re considering adding incremental compilation and parallelization in the future, but these are part of the long-term roadmap with no specific timeline yet. Other discussions have been minimal—only two people participated in the forum thread. Given that Solidity has joined Argot and the original team lead, Daniel Kirchner, is currently on leave, I’m also concerned about the long-term maintainability of the language and whether they’ve truly made the best decision for the ecosystem. More discussion is definitely needed. Thankfully, on Ethereum, you can still use other smart contract languages like @vyperlang. Source: https://www.soliditylang.org/blog/2025/10/21/the-road-to-core-solidity/ Join the discussion: https://forum.soliditylang.org/t/call-for-feedback-the-long-term-solidity-roadmap/3530