Swagrid
Member
Alright, I guess I'll engage then.I've only used copypasta one in my life so maybe that's some sort of reference that went over my head, but if you don't mind me asking, what in the world are you talking about?
I very rarely see either of these thrown about. As far as I'm aware, common consensus is to take the easy cases + some anti-diag and call it a day. However, the argument isn't about COLL as a set in and of itself. The argument is about this:I did that because I'm tired of seeing the two extremes that either COLL is trash or that COLL is OP.
Notice how this assumes, if you're working towards full ZZ-A.True, but if you're working towards full ZZ-A then COLL is a good, pretty easy place to start
COLL here is not the destination, it's an intermediate step. And a poor one.
So when you say something like this quote here above, well yes I agree. And as I've said already, I thought this were common sentiment. However, it's also entirely irrelevant to the point. This isn't about COLL for OS, or people who don't want to put in the time. This is about people who DO want to put in the time, and use COLL as almost scaffolding while they build their alg knowledge.I don't think there's any problem with COLL if you use it OS style. Personally, I don't really want to dedicate the time to learning 3x3 HPLL sequences
This block of text here starts out good - it acknowledges all of the right points. But once you start talking about giving the full inclusive picture, in a conversation about specifically using coll as a bridge between ZZ-OP and ZZ-A, well you just look foolish.Of course COLL>>EPLL isn't as good as HPLL, and a lot of times it's not as good as OCLL>>PLL. A moron could see that. There's no reason for pushing that limited statement around. Give the full picture, be more inclusive. COLL is not objectively bad; it has its purposes and it has its flaws. Learn how to work with it.
By now my point should be made. I won't sit and conclude why arbitrarily learning full COLL before ZBLL/HPLL is a bad idea, everyone already knows. But there's no need to write multiple paragraphs about the bigger picture and how my take wasn't inclusive of different solvers when we are talking about one specific use case. You missed the point.