Segwit violates practically every "best practice" of software engineering in existence. It makes wild changes to an emergent-behavior system (where it is absolutely key to make small changes at a time), it bundles unrelated changes, the adoption model is atrocious, it requires the entire ecosystem to start using a new transaction type to reap any benefit at all, it is premature optimization, it doesn't solve one bottleneck at a time, it ignores the actual bottleneck, and a future potential rollback puts all the money in such transactions in jeopardy.

I would not hire anybody who has worked on this.

Regardless, it is clear that it is not going to achieve a 95% hashpower majority, or even the new threshold of 80%, so it baffles me why it is still being discussed. It has no path to activation, and that was clear six months ago.