just to add some details: tapscript size being unlimited caused the inscriptions, which is in the witness data. before taproot, with segwit v0 there was a P2WSH script size limit, which limits the size of witness while spending a P2WSH output.

GitHub

bitcoin/src/policy/policy.h at fc06881f13495154c888a64a38c7d538baf00435 · bitcoin/bitcoin

Bitcoin Core integration/staging tree. Contribute to bitcoin/bitcoin development by creating an account on GitHub.

this whole file is about policy settings, aka filters. these settings are policy so we don't have to fork the chain each time we wanna change these. if you are asking what does this have to do with P2WSH, witness data is in the input side of the tx. so meaning of witness data is decided by scriptPubKey of the output we are spending. of course inscriptions were possible before taproot, but only really small images. or you had to split it into multiple inputs. which increases the total size and fee you have to pay. tapscript(which is basically witness space in taproot) being unlimited made it attractive as blob data storage. we can limit the tapscript size, or we can detect inscriptions specifically and other similar methods and filter them specifically, because they are using the script space as data storage, which is unintended use. parasite. knots does similar stuff.