Increasing block size does add features (and/or bugs), in the form of higher tps and whatever concomitant other new auto/adaptive regulation mechanisms come along with the eventual solution. 100k max tx size is probably only the first such
required adjustment.
In the very thread you linked gmaxwell said solution proposed by
gavin adopt an indirect and simplistic approach, to which gavin replied:
But I would REALLY hate myself if in ten years a future version of me was struggling to
get consensus to move away from some stupid 100,000 byte transaction size limit
I imposed to mitigate a potential DoS attack.
So I agree, a limit on sigops is the right way to go. And if that is being changed,
might as well accurately count exactly how many sigops a transaction actually
requires to be validated...
the bolded part really makes me laugh, though.
that said it seems that there won't be any cap to tx size for the moment.