Firefox 57 — 1
I have been using Firefox since the Netscape 2.x/3.x/4.x days, the ashes from which Firefox emerged.
I have not been looking forward to this day.
With the official release of Firefox 57, the previous way of supporting extensions is history. The previous way of customizing Firefox is history.
I understand the reasons for the changes. I am not against the changes wholesale. I want to see Firefox succeed although the Firefox developers have been doing a good job of destroying their own market share the past many years. For many users the changes will be warmly embraced.
Currently I am using Firefox 52 ESR. I have been using that version since the release. That version is supported until June 2018. Nonetheless, the proverbial handwriting is on the wall.
Possibly I will continue using 52 ESR after support ends. I am not overly concerned about security because I use several add-ons that protect my browsing sessions. Primarily NoScript to keep the bane of the web at bay. The bane of the web is responsible for much of the security and privacy invasive exploits. HTTPS Everywhere goes far to help with encrypted connections. I aggressively block untrusted web domains. Using 52 ESR past the end of life (EOL) is not a huge risk.
I am in no hurry. By the time 52 ESR reaches EOL, Firefox 60 will be available. I hope the developers will have quashed bugs and improved privacy and extensions by then.
I will start testing the new release to learn how much I have to adjust and what features and add-ons I lose.
I have been monitoring articles about the release and more importantly, writing notes from reading user comments about quirks and usability issues.
Good interface design is not about forcing on users what some user experience wonk believes. Good design allows users to decide the interface as much as possible. Yes, that means more work for developers. Humans are not clones or robots. Every person sees the world differently. While there are limits to designing flexible software interfaces, when possible user choice should prevail and not some pedantic wonk’s subjective opinion.
Consider that the Firefox developers removed the GUI control to enable or disable JavaScript. One simple check box. Removing the control served no purpose other than to satisfy egos and removed user choice.
I have three concerns with the new release: my usability preferences, privacy, and security. In addition to several add-ons, to support that foundation I have a healthy user.js file as well as many custom CSS files. What will work and break with the new Firefox?
The optimist in me says by the time version 52 ESR reaches EOL additional add-ons will be available and various bugs with privacy and security should be resolved. The pessimist in me says, “Here we go again with free/libre software. We get what we paid for.”
More to follow.
Posted: Category: Usability Tagged: Firefox
Next: One Chance to Make a First Impression
Previous: Windows 10 Fall Creators Edition