If we zoom out, we can see that beyond the illegal images argument, there is another argument that can be made against smart contract functionality (turing-complete, so not HLTCs for example) on Bitcoin in general.

Ethereum and forks like Avalanche, BSC, Polygon already do a really good job at implementing smart contracts, and 99% of the smart contract codes and programmers are using one of those chains. So why the need to implement - partially at that - an inferior alternative?



I don't mean to sound like an ETH shill by the way. This line of thinking is common sense. These moves like datacarriers, OP_CAT and so on really only benefit Ordinals, Runes and similar. They don't benefit ordinary developers like us.

If we zoom out, we can see that beyond the illegal images argument, there is another argument that can be made against smart contract functionality (turing-complete, so not HLTCs for example) on Bitcoin in general.

Ethereum and forks like Avalanche, BSC, Polygon already do a really good job at implementing smart contracts, and 99% of the smart contract codes and programmers are using one of those chains. So why the need to implement - partially at that - an inferior alternative?



I don't mean to sound like an ETH shill by the way. This line of thinking is common sense. These moves like datacarriers, OP_CAT and so on really only benefit Ordinals, Runes and similar. They don't benefit ordinary developers like us.