Wow all the hype and it's not going to help clean up the mem pool right away, I'm I getting that right?
No, you're not getting this right. This has nothing to do with "help clean up the mempool". Like the title says. The current iteration of The SegWit Omnibus Changeset does not fix the O(n^2) hashing problem. At least according to Peter Todd:
While I must admit that I was unaware of it at first, I don't see this as something problematic especially if you consider the last part. I've read some parts of that review last night and it seems very well done. Quote
We haven’t actually fixed the O(n²) signature hashing problem yet, although we’re fairly confident that we can, and there’s a open pull-req implementing the cache that we need.
Might be worth a discussion, donchathink?
Maybe. However, don't be surprise if you see a lot of 'unusual' accounts joining in to bash Segwit.I'm kidding. I just thought that with all the press in the BTC space of its implementation going live, we would actualy see it working and cleaning up he pool. That's all, just disappointing it's not ganna work out that way right now.
Again, you have no idea what you're talking about. There's no reason for it "not to work out that way right now". 
cheap coins.
