actually there was..
learn more.. instead of finding random unrelated things just to find a quote that suits your cults narrative
so here goes, lets play your game in the opposite direction
https://en.bitcoin.it/wiki/BIP_0141#P2WSH
"P2WSH allows maximum script size of 10,000 bytes, as the 520-byte push limit is bypassed. "
meaning there was a 520byte limit. that got bypassed for a 10kb limit which was implied and applied to segwit scripts which later got bypassed to allow for a 4mb when they used taproot, by not having such limitations
other things to note
Since a version byte is pushed before a witness program, and programs with unknown versions are always considered as anyone-can-spend script, it is possible to introduce any new script system with a soft fork. The witness as a structure is not restricted by any existing script semantics and constraints, the 520-byte push limit in particular, and therefore allows arbitrarily large scripts and signatures.
so now try to learn.. large scripts/signature spaces were not always possible from 2009 -2017... unlike what your cult leader tries to suggest was always possible. and then the witness v0 opcodes did come with limits and constraints. which.. for v1 were not there.
so look how things changed over the years!!
yep the witness structure has no rules. but the use of opcodes for the inclusion into the witness structure(opcodes are used to inform on which type of script system the spender wishes to use to prove a spend) used to have limits on the content included for that opcode script function of what went into that 'proof'(witness data). but with each new opcode and version they keep removing and relaxing the rules meaning the latest tx format types(aka taproot) has less rules on formatting requirements for its opcode(script types). thus that lack of format requirement(data security/integrity/validation checks) allowed any junk be added to a block
now here is a game even you can play
put a small amount of funds into
1. a legacy p2pkh address ('1' prefix)
2. a legacy p2sh multisig address ('3' prefix)
3. a segwit p2wpkh v0 address ('bc1q' prefix)
4. a segwit p2wsh v0 address ('3' prefix)
5. a taproot v1 address ('bc1p' prefix)
just enough to cover possible fees for each next spend
then i dare you to try to add a 3.9mb meme to each of those utxo spends scripts.
and see which ones can and which ones cannot.
then you will learn when the junk was made to be allowed..
and the funniest thing.
for years i have been talking about the risks of enabling the opcodes that get treated as "anyone-can-spend"
but yep the same echoed voices didnt want me to mention it and have been trying to shut me up about the possible abuses of using opcodes with less format requirements or byte limits or requirements to even need a signature in the area that is supposed to be for proof of authorisation of spending