GM - Won't relitigate past EF decisions. These are not mine to callout. Forward-looking part is. One nit: less than 10% of argot's 2025 budget went to fe (~$200k for H2). It's public info. The real problem isn't misallocation of fe vs vyper or why Fe sits under Argot while Vyper is working on generating revenue (shoutout to @nachortti for helping Vyper here), despite its adoption. The real problem is across the entire compiler stack. Fe with Sonatina, Vyper with Venom, Plank with its new IR, solx with LLVM, even Solidity is rewriting (core-sol with SAIL). They are all rebuilding the entire compiler. So many overlapping efforts inside one ecosystem, many trying to do the same thing. Yul has tech debt, sure but the answer cannot be N teams forking N IRs in isolation, all N looking for funding, taking years to be safe while the production compiler securing 500B+ across 20+ EVM chains passes the hat. Two asides: 1. genuinely glad I'm not on the solc team. Any minor change there touches that entire 500B $ surface. Huge shoutout to @solidity_lang engs. Legends. 2. shoutout to @real_philogy for collaborating with fe and core-sol toward a shared IR. Building a language is hard enough but share what is possible, especially if things take years to be safe. Anyway, what I'm doing about it: - call with argot - learning about Fe's past. - double down with @nachortti on Odin - ideally all language, compiler teams should have a sustainable path for revenue. - from my seat at the EF, working on devex. A short-term fix for stack-too-deep is in sight, while solar, solx and the solidity team work on the real long-term solution - funding languages going forward with a strategy that links the ecosystem instead of fragmenting it further 8 years in and developer pain points haven't moved enough. Time to solve them!