In fairness to Bitcoin Classic , I do need to clear up some confusion... but I also added some other distinctions which make Core the better choice of the two.
So let's set the situation straight. We have two proposals:
1. 2MB Block size - doubles the theoretical tps
introduces a new attack vector(They are aware of this and including sigop protections)- Simple change(Yet not as simple as changing maxBlockSize, much more code needs to be changes for sigop protections)
- Hard fork(Which is more dangerous)
- Smaller team of less experienced developers maintaining implementation(5 devs , with 2 very experienced)
2. SegWit- Fixes transaction malleability
- Fraud proofs
- Simpler script upgrades
- Allows for one to prune the signature data and reduce the blockchain size
- Theoretical tps possibly equal or higher than with 2 MB blocks depending on adoption(But likely an effective 1.7MB to 2MB)
- Somewhat complex; decent complexity for inexperienced users to understand(UI and usability won't be effected )
- Soft fork(are indeed safer than HF)
- Has a team of dedicated and experienced developers testing and supporting it -45+