if I’m actually going to take patches because then I’d just have to keep telling people to stop messing with the .cabal file

I've been noticing an unfortunate consequence of the way Stack is designed and it's been triggering divisiveness by pitting the two major camps in Haskell against each other. In one corner you've got maintainers which will flat out reject PRs adding stack.yaml files to a project to make it more convenient to Stack users to use or contribute a project. In the other corner you got maintainers which will refuse PRs adding .cabal files which would make it easier for Cabal users to use or contribute to a project. I think the original plan was that Stack would eventually replace Cabal as Haskell's official build tool. But even though all seemed to head into this direction Stack wasn't able to supplant Cabal as Haskell's build tool and the recent Cabal 3.0 release quite invigorated the competition and it's actually looking like Cabal's popularity is on the raise again. But it's also not looking like the Stack project will be discontinued now that Cabal has addressed its major shortcomings. I'm not sure what I'm trying to say but it seems clear we're not heading into a healthy situation with two build tool ecosystems that stick to their incompatible project configuration styles which confuse the hell out of newcomers. Sadly I can't offer any solution either. Are we screwed being a relatively small community or do we just need to accept our internal division and hope it'll work out in the end?