Windows 10: Mozilla Firefox 57 - Compatibility Milestones

I already use Chrome as my 2nd most used browser, and Edge is my 1st one of choice(and also Polarity (Powered by both Chromium and Trident)for security/privacy(user scripts) when needed, and it can be themed easily from hand, without downloading anything if you want, I have two themes published it their "store").
So why will I need Firefox in the future if it wants to be like Chrome/Chromium?

 

That's a personal choice, but all browsers need to continue to implement the latest technology to enhance security and performance.

 

Hopefully, my eye candy stays, those are the only add-ons I think will have compatibility problem, other than the already defunct Logitech Smooth Scrolling*Sad

 

I've been reading the forums on Mozillazine on this one and tbh no one seems to have a clue what will happen.
Personally I'll continue to update FF and see what the results are. As I posted earlier I only use three extensions and the only one I'd really miss is uBlock Origin (which I disable on tenforums).
I think my problem is that since I've used FF since version 3 I can't imagine using another browser, in the past I've given IE, Opera, Chrome and Edge a fair go but I don't feel at home with any of them.
Guess I'm just an old stick in the mud *Smile

 

Make that 2 old sticks in the mud (or an older stick in the mud in my case) *Wink

 

Porting thousands of add-ons into web extensions in gonna be a lengthy and tedious p•i•t•a, and that's if every developer wants to comply, and thats if Mozilla, (oops Moz://a) excepts what they have to offer.

 

My understanding is that Chrome extensions will be compatible with the new FF. You will find that a lot of the current FF extensions have already been ported to Chrome so most of the development has already been done where this is possible.

 

A lot of the theme developers don't feel that there is plenty of notice at all, so I wouldn't suggest that. A lot of developers actually share the belief that XUL isn't really slowing down the browser, it's just a management decision. Mozilla simply needs to tackle the Chrome market, which is not the power user.

In 2003, the goal was to "stand up to the man" which was Microsoft and Internet Explorer. But that's not what's in fashion now. Mobile is. So that where the real fight is, and at present, Google has it sealed. And since no one really customizes a mobile browser, Mozilla likely figures why let users do that a desktop browser. Take "Classic Theme Restorer". Apparently, Mozilla loathes its existence, because it doesn't want users trying to kill the Australis interface. Mozilla wants you to accept what's given.

I would be OK with all that if (a) I could put tabs below the address bar, (b) unhide the forward button, and (c) retain access to about:config.
*Smile

 

How do you know that? At the moment the implementation of e10s is what's driving the need to update add-ons.

 

From quotes from theme developers in conversation with Mozilla employees.

Besides, what sense does driving the need to update add-ons make, when they're about to be deprecated? That was like Dolby Labs creating Dolby S noise reduction once the compact disc had already taken over.
*Sad

 

The blog comments overall don't sound that positive.
The Road to Firefox 57 – Compatibility Milestones | Mozilla Add-ons Blog

 

Thanks for that link. I'm not a coder so I can't fully appreciate the comments, but I see that I was incorrect when I said that Mozilla was giving plenty of advanced notice to port add-ons. Apparently there are also quite a few abandoned add-ons which will be lost when support goes away. Perhaps people who want to can stay with the latest version of Firefox that works properly for them and turn off updates? Given the ongoing need to improve security and performance is there really an alternative to e10s, etc? It seems to me that isolating tabs and lowering the process integrity level are both desirable.

 

I certainly think that sandboxing and multi-process browsing may improve security and rendering. I guess those that want to avoid XUL-ageddon would just shift to the ESR release of Firefox v52. It's going to get interesting Victek *Smile

 

May get a stay of execution by using other Mozilla based Browsers however they will probably have to follow suit, unless there is a genuine Fork that has coders that can develop on the existing code?
Best to wait and see what actually happens, rather than make decisions based on doom, gloom and speculation.

 

Just want to say that "Waterfox" is slick. Can't tell the difference. How ever I can't seem to figure out how to make it my default browser. W10 does not show it in the list ???