Rule #1: The most important feature of the Bitcoin Protocol is reliability.Rule #2: When in doubt, see rule #1.
This doesn't mean that covenant functionality needs to be excluded forever, it just needs to be actually used - for example by building things on Liquid, which has much functionality for this on a compatible chain. 1
I'm personally aligned with Jimmy on this, even though I don't really like the market cap argument or the faulty taproot-annex narrative. What's funny is that the "debunk" article says exactly the same thing: changes are risky. And side-effects from this decision are still felt today - it's been fueling painful discourse between devs for 2 years now.
Take the long view, see rule #1.
Footnotes
this is why I mind Liquid less than Darth does, because I simply see it as a (risk-increased) sandbox where you can go live with an experiment. However, I am sensitive to his argument (as I perceive it) of L-BTC being an IOU, but at least they're honest-ish about that by not calling it BTC. ↩
Footnotes