Yes, as long as the block size is "regulated" to the most necessary size, the network will scale out. The Bitcoin Cash supporters say it does not matter because "Moore's Law". But what they did not consider is not all node operators are willing to do the hardware upgrades.
i actually bothered to read the bitcoin cash codebase.. and actually. if you read the code. the 32mb is known as a consensus limit.. but they also have a "regulated" limit of 2mb called the policy limit
https://github.com/Bitcoin-ABC/bitcoin-abc/blob/master/src/policy/policy.h#L19this is the same as what bitcoin core had before 2013.. 1mb consensus limit but 0.5mb "regulated limit" (in policy.h)which then went up to 0.75mb
and then in around 2015 went up to 1mb.. all without needing to fork or have big discussions because the policy was a flexcap limit
check it out consensus.h vs policy..h
so if you think that spammers can just spam their way all the way to 32mb you will be wrong. just like spammers couldnt spam thier way to 1mb in 2013 on bitcoin core..
try reading code and not reddit propaganda next time
p.S im not an advocate for bch i just like to wash away the bull crap that core and utopian propaganda sheep spout out..
funy point is core devs themselves have admitted core have issues and core is restricted on purpose to incentivise use off offchain services... but ass kissers love to brush that under the carpet
the idea of policy.h is that a limit exists, but can be moved without 2 years of debate and without needing forks.
gotta love it how even 2 years on the same scripts of 32mb by midnight, 1 gb by midnight screams are still shouted . but the real code shows something different.
it was requested by the community at satoshi roundtable 2013 that bitcoin cores consensus.h go to 8mb. and then allow policy to increment up at 0.25mb amounts as and when needed.
luke JR said 8mb is bad.. even with the enphasis of using policy.h to flexcap control the growth without neding constant debate and fork warnings
then at a later conference, called consensus december 2015 another compromise, that bitcoin cores consensus.h go to 2mb. and then allow policy to increment up at 0.25mb amounts as and when needed.
luke JR said ok.... but then a few months later.. 2mb is bad
now luke JR says 4mb weight is good but lets bring policy.h down to 0.5mb (facepalm)