I answered this
earlierSensible bounds on memory usage per tx or time based rules mitigate or solve this entirely.
If you are putting so much into a tx, then you are exceeding isStandard() rules anyway.
There is currently no solution and you are wrong. XT introduced a per transaction limit (if I'm correct). Core will address this via
BIP 143 ,which is an actual improvement unlike the workaround in XT, and a
limit. However this is node policy, miners can still create a transaction that would take too long to validate and that would harm the network.
Experience is important but it is not the only factor. If the experienced group doesn't have the right goals, then you end up reaching the wrong ones.
This comes down to the same thing actually, what is the 'right goal'? This discussion goes in circles. In any case the Core developers are definitely better than those behind Classic.