the community can fork to 2MB, core follows and everybody is happy. classic is not even close when it comes to further development.
It appears that many classic supporters are now betting on if classic reaches the 75% threshold, Core will simply go against all their principles and add the bump2mb changes to 0.12.1 and proceed with a <28 day HF. This is likely based upon the assumption that most core devs simply believe that segwit is a slightly better solution than BIP 102/bump2mb which isn't entirely true. In reality, many core devs see this HF as an attempt to remove consensus and replace it with democratic governance in which a majority can force the minority into adapting changes ... and see that as a complete failure of the project.
These aren't attempts at bluffing, we really do believe this, and thus what would likely happen if Classic activates at 75% is some core devs decide to join the classic team, some leave bitcoin entirely and slowly sell their large investments, some create an alt or leave to develop another alt, and some start making plans for the day of the fork with attack vectors on the new chain to wrestle back control..... or Bitcoin Core acknowledges Classic's accomplishment , make an announcement that they will set a planned 2MB HF 6-8 months from than* and the miners quickly turn their hashpower back to core forcing classic to quickly scramble at updating their nodes before the deadline is met and they fork off with a minority amount of hashpower.
* -- If certain conditions are met.