What's to stop the Classic team from implementing segwit? AFAIK the coding is mostly complete, and publicly available.
If Classic doesn't fizzle out like XT , they likely will implement segwit, but the difference is they prefer to do it in a HF as the developers have explained.... The earliest possible Classic can fork the network is 2 months out because the 28 day grace period. This means that If Classic starts to work on integrating segwit right away and test right away than they might be able to HF a second time to roll out segwit in 5-8 months instead of April like Core is planning. This will significantly delay improvements and benefits of segwit and work on payment channels like LN which is focused on increasing capacity.
The other side thinks SegWit is a gross kludge of code. If they just copy it, what was the point of all this? What was the point?!?
All the classic Devs really see Segwit as amazing and needed, they just prefer deploying it as a HF. Your statement is true of some classic supporters who don't understand Segwit, and have a low comprehension where they didn't realize the criticisms of Segwit from Cassic devs was aimed at it being deployed as a soft fork... which means the code is slightly more complex and less "clean".
