Michael Eriksson's Blog

A Swede in Germany

Posts Tagged ‘firefox

On Firefox and its decline

leave a comment »

I recently encountered a blog post by a former Firefox insider discussing its declining market share.

When it comes to the important question “why?”, he offers that “Google is aggressively using its monopoly position in Internet services such as Google Mail, Google Calendar and YouTube to advertise Chrome.”—which cannot be more than a part of the truth.

If it were the entire truth, this would mostly show in new or inexperienced users going to Chrome instead of Firefox, those that have not yet grown accustomed to a particular browser.

Then why is there a drop among the long-term users? Those who have used Firefox for years? Those who (like me) first used the Firefox grandfather Mosaic well over twenty years ago and then graduated to its father, Netscape?

Things like that happen either because the competition grows better (or better faster) or because the own product grows worse. Indeed, this is what I have repeatedly experienced as a user: After Netscape, I switched to Opera for a number of years, because Opera actually was a better browser, especially with its tabs. Year for year, Opera failed to add new useful features and tried to force-feed the users poorly thought-through ideas that some manager or developer out of touch with his users saw as revolutionary. Eventually, I gave up and moved over to Firefox, which at the time did a reasonable job and had over-taken Opera—not because of its own qualities, but because Opera declined.

Unfortunately, Firefox has gone down the same destructive path as Opera followed, has grown worse and worse, and the only reason that I am still with Firefox is that I use the “Tor Browser Bundle”, which is based on Firefox and recommended as the safest way to use Tor by the Tor developers.

To list all that is wrong with Firefox and its course would take far too long—and would require digging through many years* of memories of “for fuck’s sake”–memories.

*I am uncertain how long I have been using Firefox by now. In a rough guesstimate, the Opera-to-Firefox switch might have occurred some ten years ago.

However, to list some of the most important (often over-lapping) issues:

  1. The removal of preferences that should be standard, e.g. the ability to turn images and JavaScript on and off. If these remain at all, they are pushed into the infamous, poorly documented, and unreliable “about:config”—the use of which is strongly discouraged by Firefox.

    When such preferences are removed (respectively moved to “about:config”) the handling can be utterly absurd. Notably, when the setting for showing/not showing images in web pages was removed, the Firefox developers chose to defy the stated will of the user by resetting the internal setting in about:config to the default value…

    To boot, config switches that are in “about:config” often stop working after some time, merely being kept to prevent scripts from breaking, but no longer having any practical function. Among the side-effects is that someone finds a solution for a problem on the Internet, alters the configuration accordingly—and has to spend half-an-hour researching why things still do not work as intended. (The reason being that the solution was presented for an earlier version of Firefox and Firefox failed to make clear that this solution was no longer supported.)

  2. Forcing users to download add-ons to handle tasks that a good browser should have in its core functionality, while adding nice-to-haves appropriate for an add-on to the official interface… (The “sync” bullshit is a good example.) Worse: Not all add-ons are compatible with each other (or with every Firefox) version, making this road unnecessary problematic, with results including even browser crashes. To boot, any additional add-on increases the risk of a hackable vulnerability, data being leaked to a hostile third-party, or similar.
  3. Failing to add functionality that would be helpful, e.g. a possibility to disable the design atrocity that is “position:fixed” or a user-friendly mechanism for mapping keys.
  4. One truly great (and expectedly oldish) feature of Firefox is the ability to save tabs and windows when exiting or the browser crashes and have them restored on the next start. This especially since Firefox crashes more than most other applications.

    Unfortunately, the configuration of this feature is a bitch (and probably disabled by default). There are at least two (likely more; it has been a while since I dealt with this the last time) flags that have to have the right value for this to work—one of which should rightly be entirely independent*. The names of these settings in about:config and the description in the GUI are non-obvious, more-or-less forcing a user to search the web for information—if he is aware that the feature exists in the first place. And: In several releases this feature has been so bug ridden that no combination of settings has worked…

    *The one appears to control the feature; the other controls whether a warning is issued when a user tries to close more than one tab at a time. When the latter is disabled, which is very reasonable even for someone who uses the former, the former is ignored…

    Worse, without this functionality a simple “CTRL-q” just quits the browser—no confirmation, no tabs saved. For a power surfer who regularly has dozens of tabs open at the same time, this is a major issue. This is the worse since someone heavy on tabs is almost certainly a frequent user of “CTRL-w”* and there is no good native way to change key bindings—amateurish!

    *I.e. “close the current tab”. Note that “w” is next to “q” on a standard QWERTY-keyboard, making the likelihood of occasional accidents quite high.

  5. The config management is lousy.

    For instance, Firefox started with the Windows style concept of “one user; one configuration” and never added provisions to e.g. specify config files on the command line. Among the negative side-effects is the later need to invent the redundant and poorly implemented concept of a “profile”—confusing, user-unfriendly, and bloating the code.

    For instance, “about:config” provides many, many options of the type normally found in a config file, that could have been edited with a text-editor much more comfortably than over the about:config interface. However, this opportunity was not taken and the users are stuck with about:config. Actually, there are some type of files, but these are absurd in comparison with those used by most Linux applications—and it is very, very clear that users are supposed not to edit them. (Statements like “Do not edit this file.” feature prominently.) For example, Firefox uses user_pref(“ui.caretBlinkTime”, 0); where any reasonable tool would use ui.caretBlinkTime=0.

    For instance, there is so much secrecy about and inconsistency in the configuration that the standard way to change an apparently simple setting is to install an add-on… (Also cf. above.) Where a user of a more sensible application might be told “add x=y to your config file”, the Firefox user is told to “install add-on abc”…

    For instance, copying the configuration from one user to another fails miserably (barring subsequent improvements), because it contains hard-coded paths referring to the original user.

    For instance, it used to be the case that a Firefox crash deleted the configuration, forcing the user to start over… (This was actually something that kept me with Opera for a year or so after I was already thoroughly feed up with it.)

  6. The support for multi-user installations, the standard for Linux and many corporate Windows installations, is weak and/or poorly documented. The results include e.g. that all users who wants to use popular add-ons have to install them individually—and keep them up-to-date individually.

    (Disclaimer: I looked into this on several occasions years ago. The situation might have been improved.)

  7. There are a number of phone-home and phone-third-party mechanisms that bring very little value, but often pose a danger, e.g. through reducing anonymity. This includes sending data to Google, which I would consider outright negligent in light of Google’s position and how it has developed over the years.
  8. The recent, utterly idiotic decision to drop Alsa support in favour of Pulse on Linux. This decision is so idiotic that I actually started to write a post on that topic alone when I heard of it. Most of what I did write is included as an excursion below. (Beware that result is not a full analysis.)
  9. The address bar started of very promisingly, e.g. with the addition of search keywords*. Unfortunately, it has so many problems by now that it does a worse job than most other browsers—and it grows worse over time. The preferred Firefox terminology “awesomebar” borders on an insult.

    *For instance, I have defined a keyword so that when I enter “w [something]”, a Wikipedia search for “[something]” is started. “ws [something]” does the same for the Swedish version of Wikipedia; “wd [something]” for the German. (I have a number of other keywords.)

    Among the problems: If a page is loading slowly and I re-focus the address bar and hit return again, the obvious action to take is to make a new attempt to load this page—it does not: It reloads the previous page! The history suggestions arbitrarily excludes all “about:” entries and all keyword searches—if I search with “w [something]” and want to switch to “g [something]”*, I have to retype everything. Per default, for some time, the history functionality is weakened through not listing the potential matches directly, but preceding them with annoying and useless suggestions to “visit” or “search” that only delay the navigation and confuse the users. Moreover, while there used to be working config flags to disable this idiocy, there are now just config flags (that do not work)…

    *Used to mean “search with Google” a long, long time ago; hence the “g”. Currently, I use duckduckgo.

  10. The layout/design and GUI (including menu handling) have been drastically worsened on several occasions.
  11. Many of the problems with Firefox can be remedied with “Classic Theme Restorer” (an absolute life-saver) or similar “user empowering” add-ons. Unfortunately, these all use the “XUL-framework”*, which Firefox has decided to discontinue. There is a new framework for add-ons, but it does not support this type of functionality (whether “yet” or “ever” is not yet clear). Many of the most popular add-ons, including “Classic Theme Restorer”, will therefore not be able to provide the full scope of functionality and at least some of them, again including “Classic Theme Restorer”, will be discontinued by their developers when XUL is turned off.

    *In a twist, XUL was once considered a major selling point for Firefox.

    My poor experiences with Firefox and the absurd attitudes of the Firefox developers might have made me paranoid—but I cannot suppress the suspicion that this is deliberate, that the add-ons that allow users to alter the default behaviors are viewed as problems, as heretics to burn at the stake.

To this should be added that since the switch from a “normal” versioning scheme to the idiocy of making allegedly major releases every few months*, the feature cramming has increased, with a (very predictable) increase in the number of run time problems. The Firefox makers were convinced that this would turn Firefox from a browser into a super-browser. In reality, this only resulted in hastening its demise—in much the same way that a TV series fighting for its survival ruins the good points it had left and drives away the remaining faithful**. If in doubt, most people who try to jump the shark are eaten…

*I.e. making version jumps of 44 to 45 to 46, instead of 4.4 to 4.5 to 4.6 or even 4.4.0 to 4.4.1 to 4.4.2.

**A topic I have been considering recently and intend to write a blog post on in the close future.

Sadly, the delusional author of the discussed article actually makes claims like “Firefox is losing despite being a great browser, and getting better all the time.”—turning the world on its head.

Excursion on the competition:

Unfortunately, Firefox could still be the lesser evil compared to the competitors. Chrome/Chromium, e.g., has many strengths, but configurability and adaptabtility to the user’s needs are not among them; on the contrary, it follows the deplorable school of achieving ease of use through reducing the controllable feature set—the equivalent of Apple’s infamous one-buttoned mouse. Chrome is entirely out of the question for anyone concerned with privacy; while its open-source sibling chromium (in my possibly incorrect opinion) trails Chrome in other regards. I have not tried Opera for years; but combining the old downwards trend (cf. above) with the highly criticized platform shift that almost killed it, I am not optimistic. Internet Explorer and Edge are not worthy of discussion—and are Windows only to begin with. Safari, I admit, I have never used and have no opinion on; however, it is Mac only and my expectations would be low, seeing that Apple has pioneered many of the negative trends in usability that plague today’s software. Looking at smaller players, I have tried possibly a dozen over the years. Those that have been both mature and user-friendly have been text-based and simply not worked very well with many modern web sites/designs, heavy in images and JavaScript; most others have either been too minimalistic or too immature. A very interesting concept is provided by uzbl, which could, on paper, give even the most hard-core user the control he needs—but this would require a very considerable own effort, which could turn out be useless if the limited resources of uzbl dry up.

Excursion on the decline of open source:

It used to be that open-source software was written by the users, for the users; that the developers were steeped in the Unix tradition of software development; that they were (on average) unusually bright and knowledgeable; … Today, many open-source projects (e.g. Firefox, Libre-/OpenOffice, many Linux Desktop environments) approach software development just like the commercial firms do, with an attitude that the user should be disenfranchised and grateful for whatever features the projects decided that he should like; quality is continually sacrificed in favour of feature bloat (while central features are often still missing…); many of the developers have grown up on Windows or Mac and never seen anything better; … Going by the reasoning used by many Firefox developers in their bug tracking tool, Firefox appears to have found more than its share of people who should not be involved in software development at all, having poor judgment and worse attitudes towards users.

Excursion on Pulse:

(Disclaimer: 1. The below is an incomplete version of an intended longer analysis. 2. At the time the below was written, I had a few browser tabs open with references or the opinions of others that I had intended to include. Unfortunately, these went missing in a Firefox crash…)

The reasoning is highly suspect: Yes, supporting two different sound systems can be an additional strain on resources, but this decision is just screwed up. Firstly, they picked the wrong candidate: Pulse is extremely problematic and malfunctioning so often that I would make the blanket recommendation to de-install it and use Alsa on almost any Linux system. Moreover, Pulse is not a from-scratch-system: It is an add-on on Alsa and any system using Pulse must also have Alsa installed—but any system can use Alsa without having Pulse. Not only will more users have access (or potential access) to Alsa, but good software design tries to stick with the smallest common denominator to the degree possible. Secondly, at least one abstraction already exist that is able to abstract multiple sound systems on Linux (SDL; in addition, I am semi-certain that both Alsa and Pulse provides backwards compatibility for the older OSS, which could have been used as a workaround). Thirdly, if none had existed, the proper Open Source way would have been to create one. Fourthly, a browser maker who tries to dictate what sound system a user should use have his priorities wrong in an almost comically absurd manner. (What is next? KDE only? Kaspersky only? Asus only?) Notably, there are very many Linux users who have made a very deliberate decision not to burden their systems with Pulse—and have done so for very good reasons*.

*Including how error prone it is, a too-high latency for many advanced sound users, the wish for a less bloated system, or Pulse’s straying too far from the classical principles behind Unix and Open Source software. Do an Internet search for more details on its controversy.

A particular annoyance is that the decision is partly justified by the claim that statistics gathered by Firefox’s phone-home functionality would indicate that hardly anyone used Alsa—which is extremely flawed, because many Linux distributions and individual educated users disable this phone-home functionality as a matter of course. Since the users who have a system with phone-home enabled are disproportionally likely to be unlucky/careless/stupid enough to also use Pulse, the evidence value is extremely limited.

Written by michaeleriksson

July 26, 2017 at 9:51 pm

On my inactivity and human stupidity

with 4 comments

Even after returning to the Internet almost a year-and-a-half-ago I have published (or written, for that matter) very little. There are several reasons for this, including that I have decided to and benefited from cutting down on my “extra curriculars” in favour of more post-work relaxation and that I grown more and more critical as to what I consider a text worthy of publishing and a thought worthy of writing up in the first place—to the point that I must force myself to artificially lower my criteria, lest I remain silent.

The greatest reason, however, is something very different: Sheer frustration with the stupidity of most humans, with the way those more in need of feedback are correspondingly less responsive to it, and with how many of the greatest ignorants are sure of their own (imagined) knowledge and understanding. (Including the important special cases of incorrectly believing that knowledge or experience automatically implies understanding, failure to realize that understanding is almost always the more important of the three, and entirely overlooking that none of them is worth much without actual thought.) My activities in the Blogosphere have been particularly unrewarding and frustrating, and it has been a long time since I had a non-trivial activity there.

It is no coincidence that there are many sayings or quotes expressing the principle that the fool is cock-sure and the wise man doubts—nor that the Dunning–Kruger principle has gained fame among those who do think. (Executive summary of Dunning–Kruger: Ability at A goes hand in hand with the meta-ability to judge ability at A.) Indeed, one of the few things that give me some amount of personal pride is simply that I belong to the small minority of people actually willing to actively challenge their own opinions and modify them as time goes by.

The examples of this are very common and the effects extremely demotivating to me. It is proverbially better to light a candle than to curse the darkness (and I have long tried to live by this claim), but there simply comes a point where it is hard to keep it up—especially, since there are many ignorants not only impervious to candle light—but who actively put out candles lit by others. Those who are familiar with my writings will know that I have written a lot about censorship—and the sad truth is that there are many blogs (notably feminist ones) who simply censor comments that have a dissenting view. This includes even polite comments using factual arguments, links to statistics, pointers to logical errors, … Indeed, often the comments that are the more likely to convince a third-party are the ones preferentially censored… Specifically in the realm of political correctness (in general and to some degree) and feminism (in particular and to high degree), there appears to be no willingness to actually look for the truth. Instead, pre-formed claims are pushed with great insistence, even when no more justified than e.g. the claims of a creationist: Both kinds live in their own special world where some things just have to be true because else they would find themselves in another world or have to face possibilities that they cannot cope with. Scientific proof, logical arguments, whatnot, are all secondary: The truth that these point to is abhorred and therefore they must, ipso facto, be faulty. It is inconceivable that God did not create the world; it is inconceivable that differences in outcome could have any other explanation than differences in opportunity. Anyone claiming otherwise is uninformed and should let himself be enlightened—or an evil liar deliberately trying to ruin the game, a heretic, a sexist, … Meanwhile, those wishing to “enlighten” the dissenters typically give ample proof of their own ignorance, undeveloped ability to understand arguments, and lacking prowess with critical thinking. A particular annoyance is the constantly recurring claim that those who criticize feminism (more specifically gender-feminism and feminist populism) are ignorants who must be exposed to the truth—when most critics (at least in Sweden) actually grew up under feminist indoctrination, long took feminist claims to be true, and only over time developed a more nuanced world view, by means of critical thinking, exposure to more scientific information, personal experience contrary to the feminist world-view, and so on: If the feminist claims about e.g. rape statistics, domestic violence, earning capacity, discrimination against women, …, were true, then almost everyone would be feminists—but I have over time learned that these claims for the most part are invalid. (For varying reasons for different cases, but often including hiding vital details that radically change the interpretation of data, misreporting of data, use of unsound methodology and non-standard definitions, statistics extrapolated to different areas or times without verification of relevance, and even statistics simply made up.)

These problems, however, are by no means limited to the Blogosphere, nor to the politically correct or any other ideology or religion. No, stupidity, irrationality, incompetence, and so on, permeate the world and all its aspects, the main question often being whether a certain phenomenon is explained directly or just indirectly by such factors: Is the advertising industry filled with idiots or does it merely try to convince idiots? (I suspect that it is a bit of both: People of highly disputable competence and judgment trying to preferentially convince the most stupid, irrational, and uninformed consumers.)

Even in software development, stereotypically associated with the gifted and the border-line autistic, there are few who have the competence level they should have and many who have a good standing through social relationships and despite their lack of skill. About five in ten of the colleagues that I have worked with have been so poor that I would simply not have considered them an option, had I been setting up a new team. No more than one in ten is someone I would give a blanket “yes”. Another one in ten may be a border-line case, picked or rejected depending on the available alternatives. The remaining three might do if nothing else is available and a sufficient mentoring and reviewing could be guaranteed. Even those worthy of a “yes” are typically lacking of the competence they should have, for the simple reason that they have the competence level of a worthy developer—but typically work as lead developers. Notably, most of them have a very limited own understanding, instead basing their decisions on rules, recommendations, or things that they have read somewhere without giving sufficient thought to e.g. why the recommendation is made and when it does not apply because the underlying cause for the recommendation is irrelevant. For instance, The lead-developer of a team that I was assisting a while ago was highly surprised by the suggestion of replacing an ugly set of conditionals with a look-up in map—apparently, he was unaware of this obvious and well-established technique that even a junior should (but rarely does) know. Going outside the “yes” developers and the border-line cases, things deteriorate very rapidly. The average developer has no feeling whatsoever for what makes good and poor code, does not use the benefits of polymorphy over if-statements, uses copy-and-paste when he should write a new method or class to abstract the same functionality, writes test cases that are next to useless through checking the implementation instead of the interface, …

It is the same with other professions—software developers still do better than most other groups. Looking at most business graduates I have dealt with, I marvel that they actually did graduate… Most are lacking in knowledge, almost all are devoid of understanding, and areas such as critical thinking are uncharted territories. Large egos and great efforts to create an appearance of competence are more common.

A particularly frustrating problem: The few of us who actually do strive for understanding often see problems, opportunities, solutions, …, that others do not. However, because the ignorants are in the majority, the minority is considered lacking… (E.g. through being seen as obsessing with unimportant details when these particular details actually are important, or as being wrong in a dispute for lacking some insight of the majority—but where the reason for disagreement is that the minority has this insight and several more that the majority is lacking…) A project I worked on last year had me crawling up the walls for frustration for this reason (in several areas, but mainly with regard to Scrum):

I had spent some considerable time deepening my knowledge and understanding of Scrum and was actually enthusiastic (rarely happens with me…) about testing this and that, in particular seeing what gains might be possible through systematic inspect and adapt. My efforts where almost entirely blocked by a team that had no understanding of Scrum but merely followed a certain formulaic approach, leaving inspect and adapt (the very core of Scrum) entirely by the wayside. This regrettably extended to both the Scrum Masters that the project saw: The first had masterly conned large parts of the company into believing she was a true expert, making anything she said an ipse dixit during any discussion. In reality, she was a disaster in her role, not merely through failing to understand inspect and adapt, but also through failing Scrum in several critical regards, notably including trying to prescribe what the developers should do and how they should do it (and not limited to Scrum at that). The second had no previous Scrum background, but went through a crash course consisting of tail-coating number one for two weeks combined with some informal tutoring of the blind-leading-the-blind kind. Discussions with her were even less productive, with an even more limited intellect and the one implicit argument of “number one said and number one is the expert”. No: Sorry, the only one in the project who had any claim whatsoever of being a Scrum expert was yours truly—I was the only one who had bothered to go beyond superficial knowledge and actually gain an understanding of the principles and ideas, as well as the only one who seemed to actually evaluate how well or poorly something worked.

Many examples of how stupidity rules the world can be found in the UIs of modern software programs, with explanations coming to a high degree from the made-for-idiots camp, but also, if to a lesser degree from the made-by-idiots camp (e.g. through not understanding the benefits of separation of concerns, not having knowledge of alternate paradigms, or undue prejudice against e.g. command lines). Take web browsers: For a considerable part of the post-2000 period, I was a dedicated Opera user—Opera delivering superior functionality and speed. However, for each subsequent version, Opera grew less and less user-friendly, to the point that I threw up my hands in anger and reluctantly switched to what seemed the least of the many evils: Firefox. Unfortunately, Firefox has continued with the same user-despising trend as Opera. Negative developments include, but are by no means limited to, removing the options to turn images and JavaScript on/off from the GUI, necessitating a visit to about:config, or reducing the usability of the image filtering severely by removing the generic black-/white-list system in favour of a rights system where rights can only be set for the domain of the current page (but not for e.g. a domain that provides images displayed on that page). Worse, as I recently discovered during the update of an older system, when these were left in the “off” position in a version that had the toggle in the GUI, an upgrade to a version with the toggle in about:config would automatically, without asking the user, and in direct violation of reasonable expectation, turn them on again—absolutely inexcusable! Generally, Firefox has a severe usability problem through forcing central functionality into unofficial plug-ins that have to be installed separately. Yes, plug-ins are great. No, it is not acceptable to move functionality central to the product to plug-ins or to force the user to install a plug-in for something that should be done through a setting. (However, installing a plug-in to provide a more advanced version of the central functionality is acceptable. A JavaScript on/off switch is a must in a browser, and a per site toggle very highly recommended, but the full functionality of the NoScript plug-in is legitimately put in a plug-in.)

While Firefox removes central functionality, it also includes more and more non-central functionality that rightfully should be (but is not) in a plug-in, e.g. the “sync” functionality. Or what about the many, many URLs that can be found under about:config for a variety of unspecified tasks, some of which is highly likely to include unethical “phone-homes” or definitely expose data to Google (a by now entirely untrustworthy third party)?

One of my main beefs with Firefox since day one has not improved one iota over possibly some five years: I like to run different instances of browsers for different tasks (at home using different user accounts, at work at least using different profiles). Under Firefox this means a lot of unnecessary work. For instance, installing a certain plug-in for all users is not possible (resp. there is an alleged way, but it is poorly documented, it is non-obvious, it requires far more work than a single-user installation, and it, judging by my one attempt a few years back, simply does not work). Profiles, in turn, are very poorly thought-through, having no official means to copy them, requiring command-line intervention to run more than one profile at any given time, and, when push comes to shove, merely solving a problem that would not have existed in the first place—had Firefox made proper use of config files. If it had, one could just tell it to use the settings from file A for this instance and File B for that instance, with no additional programming or a cumbersome profile concept. Whether using profiles or additional user accounts, a major issue is to have to go through a good many settings for each instance: Settings is the most natural thing to export and import between parallel instances—but this is not allowed. What Firefox provides is a means to export bookmarks and similar—but that is near useless for any practical use. (Yes, this could be handy when e.g. moving from computer A to computer B. However, then I would most certainly want the settings too. For parallel use, in contrast, the settings are far more important: I may need to alter one or two individual settings between instances, but the website visited will be almost entirely disjunct.)

One of the most atrocious examples of stupidity is the German “Energiewende”: A massive and costly intervention has been made to move energy consumption and production to “renewable energies”, and many criticize it already for the costs or the many implementation errors that have unnecessarily increased the cost or distributed it unfairly. Personally, I could live with the costs—and have to admit that the increase in renewable production capacity has been far more successful than I thought it would be. Unfortunately, there is one major, disastrous, and incredibly counter-productive catch: The production form which has been replaced is almost exclusively nuclear power—while the use of “fossil fuels” (especially coal) has actually increased (!). In other words, the net-effect of this massive and costly intervention is increased pollution… (Notably, very few people are aware that fossil fuels do far more damage to the environment and cause far more human deaths on a yearly basis than nuclear power has in its entire history, including the accumulated effects of Chernobyl and Fukushima.)

I could go on and on from a virtually endless list of examples, causing the writing of this article continue for far too long and ensuring that almost all potential readers will have the feared “to long; did not read” reaction. (Not that I have any illusion about the proportion still reading, even as is.) Instead, I prefer to make a cut here, but I will make some honourable mentions that I had originally intended to include with one or several paragraphs each:

  1. Deutsche Bahn (“German Railways”) demonstrates so much incompetence on a daily basis that I could write several articles on that topic alone.

  2. Museums used to be a way for those with an interest to actually learn something. Today they are rapidly degenerating into cheap entertainment–and they pride themselves with their “family friendliness”, which means that those who try to learn have to cope with children running around and screaming without anyone intervening. In many ways, what the typical museum of today does, is antithetical to the purpose of a museum…

  3. The abysmal state of groups like journalists and teachers, who should be among the intellectual elite and are so often so embarrasingly poorly informed and poor at thinking.

  4. Belief in various superstitions and pseudo-sciences, e.g. astrology, homeopathy.

  5. The lacking queue management in stores where a further checkout-counter is only opened when the queue is already several times as long as it should be—not when it becomes clear that the queue is starting to get out of hand.

Written by michaeleriksson

October 13, 2014 at 8:48 pm

Abandoning Opera

with 6 comments

For at least eight years, I have been an Opera user—and for much of that time, I have considered it the best browser around and strongly recommended it to others.

Today, I throw Opera at the metaphorical garbage heap, to focus instead on Firefox. This following a transitional period of roughly six months, where I have been using Opera and Firefox in parallel.

Why so?

Well:

  1. Firefox has improved over the years. Most importantly: It no longer deletes (!) the config files when it crashes—an inexcusable programming error, which was present for at least several years (and which has been a strong influence in my repeatedly interrupting experimental Firefox use in the past).

  2. Firefox has a great number of plugins. While most of these are of no value, some are extremely useful, notably Vimperatorw and NoScriptw. Opera has very little “external” functionality, which makes it crippled in comparison (a plug-in framework of some sort was recently announced, but the success is too uncertain and the time frame too long to sway me).

  3. On that line: Firefox has Vimperator…

  4. Opera has a number of annoying behaviours, e.g. concerning the address bar (which tends to grab focus when it should not and keep focus after it has been told to let go).

    Specifically, the last straw that now makes me abandon Opera: Today, I loaded about a dozen tabs from an unusually slow website. I moved onto the first tab, with a half-loaded page, pressed the space bar to jump over a contentless introduction—but instead of jumping downwards, the address was overwritten with a space. (Incorrect initial focus.) I then clicked on the page, switching the focus to where it belonged, and pressed space again—only to see yet another space added to the address bar. (Counter-intuitively, two clicks are required to “unfocus” the “activated” address bar.) Within a few minutes, this repeated on most of the remaining tabs—and since this was the umpteenth time this happened, the last straw was in place.

    (Should I not have known better and adapted? Possibly, but using a computer is a largely automatic procedure with me: If I wish to scroll down, my fingers do the right thing without thought, just like my legs do the job of turning a corner without thought. If someone or something screws with standardized behaviour, I am thrown off. Consider trying to turn a corner when the legs go in the opposite direction of what they do on a normal day…)

  5. Opera has a user-despising attitude to features of “we know best”, “the more, the merrier”, and “let us shove the features down the users throat”. (A common problem in world of software, see also my writings on software development.) Notably, these problems have become worse from release to release, and (in some ways) Opera is actually deteriorating.

    The worst example is possibly “fast forward”—a function that when activated tries to jump to the next page (according to some heuristic). This is not a bad thing in itself (at least, were it more accurate…); however, this function has been mapped to a number of keys in a non-standard way—including the space bar. Now, the space bar, in a text-reading context, means “scroll one page down in the current document”, in a tradition going back to at least the 80s and used in all browsers I have ever made more than casual use of. In Opera, the meaning has been altered using fast forward to “scroll down or skip to what I incorrectly believe to be the next document”. Not only does this break standard in-document navigation, but it is also extremely confusing, because the user is never told about this non-standard behaviour.

    (Generally, Opera has many odd and unexpected key mappings.)

    A more subtle, and largely unknown, example is “fraud protection”: Unless explicitly de-activated, this feature “dials home” concerning every site visited (!) to check the credibility of the site. This is done with good intentions, but causes unnecessary time delays, opens a very wide gate for abuse, and brings little benefit in practice: Before I found out and turned it off, I cannot recall it giving me as much as one single warning…

  6. Two strong arguments for Opera in the early days, speed and tabbed browsing, are moot today: Tabbed browsing is standard, and any speed advantage Opera has is rarely detectable in practice—and Chrome is alleged to be even faster. (Do no use Chrome, however: There are too many potential security problems.)

  7. Opera is a commercial tool, while Firefox is Open Source. Now, I am not ideologically bound to the use of Open Source software, let alone Free software; however, my experiences have shown great advantages with Open Source, including faster bug fixes, higher quality, and a greater consideration for power users. Further, while I have seen no signs of malicious abuse using Opera (e.g. spying on users), it can never be ruled out—and is a very real possibility for the future. Firefox, in contrast, would be exceedingly unlikely to even try something like that—and would be unable to do so for long without being exposed.

  8. If I have not made the point: Firefox has Vimperator.

The two things still speaking for Opera: Firstly, it has a few very handy functions (e.g. “fit to width”), which Firefox still lacks or only gives an inferior emulation of, with our without plugins. However, these are things that can be sufficiently worked-around to avoid a knock-out victory’s over-coming the heavy point deficit in the twelfth round. The one severe weakness that Firefox has is the lack of a decent tool to match keys to functions—but Vimperator solves parts of that problem. Secondly, Opera does run better out of the box (after some time has been spent on de-activating various features) and has an easier configuration. However, this short-term advantage does not carry-over to the long-term.

Written by michaeleriksson

November 2, 2010 at 3:03 am