Why do you keep alienating your user base with worthless UI changes?

Question

If it weren't for some add-ons that I've come to depend upon which are not supported in Chrome, I'd have switched long ago. But version 29 is the last straw. If I can't get version 28 re-installed and working again, I'm quitting FireFox for good.
You claim that FireFox is so damned customizeable that it's easy to revert to the v. 28 UI, but that's simply not true. First of all, it requires an add-on which breaks other functionality. Second, that add-on doesn't restore everything. And Third, there were about:config setting that did fix some of these things (e.g. browser.tabs.onTop) but you've broken/removed those settings in v. 29.
Why not simply make all of these things configurable in about:config, like browser.tabs.onTop? What's the point of forcing us to use an add-on, where we're dependent on a third-party developer who clearly didn't get it quite right because he's broken other things? Indeed, the support page even says that the only way to get TabMixPlus to work is to revert to the stupid curved tabs - I can't have square tabs and TabMixPlus, so right there it's impossible for this add-on to restore everything the way it was.
You've broken FireFox for the last time, and as I said if I can't get v. 28 back I'm quitting you for good. I've already abandoned you on Android because you can't seem to make that work - it crashes all the time on both my phone and my tablet - and you're ruining what once was the premier browser.
So, again, my question is: Why do you idiots keep alienating your user base with worthless UI changes? I believe that you developers are making changes for change sake, and you're so close to them you think everyone will think your crap UI "improvements" smells like roses. Well, they don't - they stink. If FireFox is so damned customizable, and you think your ideas are so fantastic, why not show people how to configure FireFox the way you prefer, rather than force the changes on everyone and tell us who don't like it to figure out how to put it back on our own. And if FF 28 wasn't flexible enough to get the look and feel you prefer with simple settings changes then you should have worked on making those changes possible, not worked on hard-coding them so nobody can change them.
More importantly, perhaps you should concentrate on fixing bugs, instead. You should not have released v.2 until you'd addressed all bugs from v.1. BugZilla documents a history of bugs carrying over year after year. That is unprofessional. You still have memory leaks after all these years, forcing me to re-start FireFox on a regular basis - that is simply irresponsible. Yes, you've addressed them. Yes, you've made things better by not loading pages after a re-start until we click on that tab. But those are bandaids - you haven't fixed the actual memory leaks! To claim we must accept your willy-nilly UI changes to get security enhancements is ludicrous in the face of these memory leaks.
''Title was edited by a moderator due to language. See the [http://support.mozilla.com/kb/Forum+and+chat+rules+and+guidelines Rules & Guidelines] .''

Answer 1

If you're on a 64bit OS I highly recommend waterfox. If not you can have a look at cyberfox and palemoon. All of those are built on firefox but are ignoring the terrible gui changes.
Good luck and let me know how you get on.