First principle: It is not of you business how I use my money with other consenting parties. You might not think it's useful. Good for you. It's not your decision.
Second principle: Smart contracting comes from BITCOIN. Those other systems are clones of Bitcoin, that chose to hype up some parts the copied or expanded on. Their investors-- which may well include you-- routinely act to undermine Bitcoin. Including perhaps, through subversive manipulation campaigns on social media to hobble bitcoin's functionality.
Third: Those other systems are generally technically incompetent massively premined frauds. They are objectively not good, their implementations have lost hundreds of millions of dollars through totally avoidable errors, including some that Bitcoin has solved since day one (like addresses having checksums).
These moves like datacarriers, OP_CAT and so on really only benefit Ordinals, Runes and similar.
How does the op_return stuff have anything to do with ordinals or benefit it in any way? Why are you talking against OP_CAT in a thread promoting knots when luke has publicly committed to activating op_cat?
Back in the thread,
There was a proposal to implement a check that pubkeys must be "real" (i.e. be on an elliptic curve), which means additional ressources needed for tx validation, but it could be worth it if it really was a solution to the problem.
There are several fairly straightforward ways to transform arbitrary data to and from an indistinguishable valid pubkey. One is in the bitcoin codebase already for the P2P encryption. So what, permanently increase the validation cost of every txn by 1/4 or something to make the opponent copy and paste a bit of existing code? So not only would that fail, it would also make things worse since at least now a node could expand its definition of unspendable outputs to include the ~half of these that aren't valid points and exclude them from their UTXO set. But if blocked and then they move to adjusting the encoding so they're always valid points (or just changes to make them 256 bit "script hashes") this option goes away. Keep in mind that none of the 'spammers' are particularly fee sensitive or they'd absolutely not use Bitcoin at all.