Every change breaks someones workflow [1]. It sucks, but it happens because we need to acknowledge a point when the current system holds back progress more than the headaches introduced by a new system.
[0]: https://blog.mozilla.org/addons/2015/08/21/the-future-of-dev...
No it hasn't: Firefox still doesn't ship an API capable of supporting many existing extensions. The developers of those extensions haven't had three years to port; they still can't port.
I really like how fast the new Firefox is, but I won't use it until Keysnail works.
JS-based (crippled IMHO) vertical tabs are also in Chrome. Why would someone switch from Chrome to Firefox to use a crippled extension?
I hope I am wrong but I don't think Firefox will be able to increase their market share. They may be able to stop losing their market share, which is not really a huge achievement.
And I doubt they're ever going to.
It's the Design Disease: Once a company has it in its head that it Knows Better, anyone who ditches their way for a different one is Wrong, just... Wrong in some way the company thinks is objective, based on whatever Design it has in its head, and must be brought back into the fold.
How tabs work is Design. Design must not be questioned. If you want your tabs to open such that you get a new tab right beside your current tab, instead of over a dozen tabs away at the end of the tab bar, you're Wrong, and having more than three or four tabs is Wrong, too.
They can say that Firefox is faster. I say it's easy to be faster when you're not solving the whole problem.
NoScript, Session manager and Self destructing cookies are the hurdles to clear for me - the rest I'll miss but can probably get by without. Note that both the session and cookie manager are in fact features that should already be part of Firefox and are not. And when I say 'clear', I mean functionally equivalent in all regards to pre 57 (NoScript fails that test).