I'd have to say that I'd rather go with Segwit even with all the times that the devs being too close to blockstream and so on, I still feel that they're the best set of people to actually help the bitcoin network with their scaling solution.
I feel as if BTU is just going to be a way for the majority of miners (Chinese) and Ver to be able to fight to make some crazy money off of hard forking bitcoin if they're able to hit the magic number of 51 percent, or more around 70 if they want to actually do it without an issue.
I just don't like the centralized aspect of BTU, I don't feel thats what Bitcoin has and ever should stand for.
SEGWIT!
you do know that the BU code is ok to work with a dozen differing brands to stick to a PEER open and diverse network.
but blockstream(core) want segwit code to set themselves up as the upper TIER main network auditors of the blockchain and have everything non-core as the down-stream filtered second class nodes.
core also have all the excessive ban hammering and orphaning code,(bip9 and UASF) not the other way round.
its core that bypassed hard(node and pool) and just went with soft(pool only).
and even this week core want to go a step further by now threatening to move away from PoW if pools dont vote segwit.
pretty much removing community choice and instead using threats.
non-core dynamic nodes want hard(node AND pool) consensus..
so dont blame pools for having the only vote for segwit.. core gave them that privilege over segwit..
where as the dynamics, IS a node and pool required vote so pools cannot alone force dynamics
core also removed reactive fee estimates and replaced it with average (meaning no drop in fee when a block demand is low because the price is spread out over many blocks average. thus not helping lower fee's when demand suddenly drops.
core removed priority, and raised the minimum spend.
oh and the real clincher
non-core nodes(real baseblock increase) that want dynamics are using real consensus hard(node and pool) so even if pools got to x%.. the nodes still are needed to approve it. so all this 'chinese miners are forcing the issue', only applies to segwits activation/non-activation.. due to core decision to give pools the only vote for segwit.
but dynamics needs node approval too. so pools cant just force dynamics.. pools need nodes there too, otherwise you will see alot of orphans and alot of pool timewasting making blocks that never get added to blockheight if nodes are not there to support it.
non-core implementations set no deadlines or made threats of banning the network.
if any implementation wants to support dynamics without downloading a specific brand they can use their own favourite and just add a few lines of code, yep even core can tweak a few lines and be dynamic compatible..
but segwit is a complete rewrite so anyone wanting segwit has a bigger job to rewrite to be segwit compatible and then be thrown into "its not peer reviewed your team are cramp" war game.(unless you enslave urself and just use their code like a good little sheep they want you to be)