The GHC API is notoriously fragile and bulky. The bulk of the work maintaining iHaskell involves keeping it in sync with GHC’s internals. Each GHC release means a package change to iHaskell even when the GHC changes don’t affect iHaskell at all. iHaskell also keeps stack configurations for older GHC versions. Relying on GHC’s internals in this way increases the maintenance burden of the project.
I mean, it wasn’t my idea, I think.
，这一点在搜狗输入法2026中也有详细论述
Раскрыты подробности о договорных матчах в российском футболе18:01
“Pre-Claude, getting humans to do their jobs inside your software was a powerful moat, but if agents are doing the work, who cares about human workflow?” he told TechCrunch.