And the punchline is always a soggy: "I'm seriously reconsidering".
Post would be much more effective if you just switched already, and discussed your experience having done so.
And the punchline is always a soggy: "I'm seriously reconsidering".
Post would be much more effective if you just switched already, and discussed your experience having done so.
That said, I like Canada a lot and have spent a lot of time there. It is quite nice
safari is also incredibly fast compared to chrome and ff. i love ff, but since starting to use safari i honestly don't think i could switch back
On Sierra, you can reenable favicons with MySIMBL [1] and SafariStand [2].
[1] https://github.com/w0lfschild/mySIMBL [2] https://github.com/anakinsk/SafariStand
- forced bundling of pocket/readability,
- forced bundling of hello,
- forced and heavyweight extension signing (I understand them wanting to sign extensions in user profiles; but the extensions installed by root should not need that - this killed the config extension for FreeIPA, for example),
- I understand their desire to change their extension model, but killing many popular extensions is not a way. How it was communicated was a great example of hubris,
- DRM support should not have been the default choice,
- but MSE WebM with VP8 and VP9 still doesn't work,
- the Australis redesign was controversial.
(And from personal interest standpoint: still no Web Components support? still no WebP?)
I think they dropped Hello altogether.
Extension signing is not forced though, can be toggled from about:config.
In my opinion WebExtensions is a last ditch attempt to gain users and devs. If FF abandons XUL, WebExtensions will be the ONLY STANDARD way to write extensions. But in their defense there are active discussions about adding new APIs to enable more powerful integrations.
DRM is off by default on fresh installs, AFAIK and is user toggleable in Preferences unlike being hardcoded in Chrome and Edge.
Extension signing can be disabled in about:config, but I think the pref ("xpinstall.signatures.required") only works in the Firefox Nightly and Developer Edition channels.
EME DRM is enabled by default in Firefox, but it won't work until the DRM blob (Google's Widevine CDM DLL) is automatically downloaded about one minute after Firefox launches. Here are instructions for disabling EME DRM and uninstalling the Widevine CDM:
On the non-beta version? It's not supposed to be toggleable.
Unfortunately that is no longer true. Their argument was that users could be tricked to disable it, or run extensions that disable it. So to cater to the lowest common denominator user they completely removed the option for all users of Firefox.
The alternatives are the non-Firefox (unbranded) Firefox builds or using an alpha version of Firefox (developer version).