And the primary idea behind that fork is to improve throughput. What's your alternative? Would you rather developers didn't work on scaling Bitcoin at all anymore?
Now you're changing the topic of discussing entirely.
(...)
The problem is the oversight that left some rules "loose" and enabled this attack vector which Ordinals is exploiting to perform their attack.
The two points are linked. Scaling generally requires extensible code. If you make it too rigid, there's nowhere to grow. If you want a dinky little bonsai tree, then sure, strict and disciplined is the way to go. But we need something bigger than a bonsai tree, here.
If you propose painting ourselves into a corner, development-wise, but the devs have other ideas on that matter, guess what the outcome is going to be.
It's all building blocks. Incremental steps to better things. Try not to let this incident cloud the big picture.