I think the problem is black/white thinking on both sides. There's a difference between spam and legitimate non-monetary use cases. Ideally, a reasonable balance could be found by earest and pragmatic developers and Bitcoin service providers. Uncapped OP_RETURN with no filters is too extreme and an obvious hazard. I support L2s, timestamps, etc. but they don't need such extremist and dangerous default settings.