I've ended up with 57 on current, and I'm not really happy with it. I can't tell any difference in speed, they seem to have changed things just for the sake of change (oh, lets have square tabs like chromium since that's the trendy thing to do these days) and changed icons for no real reason.

I could get past all of that if every time I loaded it I wasn't confronted with a barrage of MB's of data coming through that I don't know where it's coming from. I have about:blank as my home page, blank (and turned off all the new options they 'added in' for new tabs) have no data sending enable for crash reports, yet as soon as I load it the lights on my router start flickering like a christmas tree.

Well I took the plunge. Just had to try and screw things up. I have mozilla-firefox in the slackpkg blacklist file to make sure I did not accidentally upgrade it. Today I commented it out. Before upgrading I took the precaution of making a backup of the profile directory.

I like it, but it's going to take some getting used to. Tabs on top for one, Also noted the reload button has moved to were it used to be ages ago, my hand now has to be retrained yet again. Extensions? Yikes! It doesn't really hit home as to how many you have until they are gone (disabled). At least you can still access them as legacy extensions to help with finding possible replacements, that "find replacement" button btw is worthless. Need to search add-ons site for possibles. I've already found a few, started using them before taking the plunge. I found a replacement for a search add-on I use a lot sadly it can't use the engines already installed since mozilla has not allow the WebExtensions access to that... so you have to add them to the add-on. The new add-on has plenty of preset search engines but of course only a couple I use. At least it's customizable.

All of that said, I am back to 56.0.2. Decide to wait a bit longer. Thanks to ruario's script I was able quickly create a 56.0.2 package.

True, missing extensions could be a real problem for many users. The positioning of the reload button is an easy one though: right-click, customise, and drag it wherever you like.

Hmm... true, but... it was positioned inside the URL bar. No sure it will let me do that. ;) I'm okay with where it is, it my hand that's not. :)