Tezos has some problems.

• There is no formal verification. - sure functional languages are cool, does not make verification much easier if nobody can write code.
• IP issues
• It can still hardfork.

See my comprehensive post below for more information.

Yes, there is no need to hardfork Tezos in a potentially controversial way to incorporate innovation and new features. This has the potential to eliminate the "stalemate" type of situation happening right now regarding Bitcoin scaling. Don't let this post be a complete criticism of the idea. I think systems like this are the future. Although, systems like this do not need to be exclusive to Tezos, this style of consensus could be implemented inside of Ethereum for example.

Tezos hopes to mitigate the pressure points that lead to hardforks. If there is a detrimental bug somewhere in the consensus code, maybe something like the 2010 overflow bug and fork will need to happen to Tezos, let's just hope it is not controversial. - sometimes there won't be time to vote.

Hardforks can happen.

https://steemit.com/tezos/@kyle.anderson/we-don-t-need-to-hardfork-a-questionable-story-about-tezos-ico-july-1st