Adjusting to Firefox

I’m giving Firefox another shot as my default browser.

In December, when Microsoft announced they’d be using Chromium for their future browser, I was partially happy because it meant one less browser engine to worry about.

I was also partially unhappy because it meant one browser engine had that much more power in deciding the future of the web.

In January, when a program manager at Microsoft suggested Mozilla “get down from their philosophical ivory tower” and embrace Chromium, I started thinking more about what it meant to use Firefox rather than Chrome.

So here I am. A Twitter search shows it’s been just over a year since my last attempt, which lasted 2 months. I didn’t write a blog post that time, but instead mentioned two things in a tweet:

  • Chrome’s dev tools are still better (for me).
  • Firefox started off fast, but has been really clunky lately.

How helpful of me.

It looks like I also made attempts in 2012, 2014, and 2017. The frequency seems to be increasing? I should remember that Firefox was my default browser for years before Chrome came out. Maybe it will stick this time. 🤞🏻

My first impression upon opening Firefox 65 was that everything is boxy and feels sluggish. I have to remind myself that I’ve spent thousands of hours in Chrome and need to make time to get used to something new.

My first step was to switch to the light theme, which feels a bit better.

In general, typing feels slower in Firefox than in Chrome. Not a lot slower, but somewhat like walking through a mud. I dunno.

My immediate thoughts are all around look and feel. The spacing between bookmark icons and text in the toolbar is a bit off and the line height doesn’t feel right. Again, using Chrome for thousands of hours has my brain looking for something similar.

I do think the Firefox team would benefit from spending some more time tweaking defaults around text.

The default Firefox interface with the light theme applied.

I was able to immediately remove that “flexible space” to the left of “New Tab” through the “Customize” interface, which provides a nice amount of customization.

At this point I stumbled into the world of customized Firefox and started editing my userChrome.css file to make small adjustments. It was easy enough to tweak the toolbar height and adjust some line coloring. This is a task that could really be a time suck if you aren’t careful.

And then I found MaterialFox!

The Firefox interface with MaterialFox applied.

I replaced my userChrome.css file with the entire chrome directory provided by that project and now Firefox looks almost exactly like Chrome. I’m not sure if that’s a great thing, but it’s at least making my brain feel okay, so I’ll take it.

The look and feel is much better now, I just need to get used to whatever my brain is perceiving as sluggish.

The only other small annoyance right now is that in Chrome I can toggle the bookmarks toolbar with CMD-Shift-b. This toggles the bookmark sidebar in Firefox. There is no keyboard shortcut for toggling the bookmarks toolbar and I don’t think there’s a way to assign one without installing an extension, which I’m hesitant to do right away.

I’ll save that one for later and see how often I really want to toggle it.

That’s it for first impressions. I’m going to do my best at giving it at least a month. I haven’t used the developer tools yet, but I’ll try to stick it out and open Chrome for troubleshooting if I really need to. I’ll plan on keeping a running log of issues to publish if I decide to switch back so that I know what to check for next time. 🙂

Assorted Resources

These came in handy today.

  • Find your profile directory through “Help” -> “Troubleshooting”
  • If you use a custom userChrome.css file, don’t get smart and change the namespace URL to be HTTPS. It won’t work.
  • To inspect the styles for the “chrome” of the browser, enable the Browser Toolbox.

Initial conditions, Wonderlust, and the art of noticing

Where do you look when you walk into a space for the very first time?

Jake poses this question at the beginning of his Initial Conditions, a post that provides an overview of the inspiration used for establishing a set of “initial conditions” for new members joining the HYPER lab at WSU.

Initial conditions, as a mathematical term, is an interesting way to describe the scope of what the lab is trying to document, especially if you think of a lab—or any community—as a dynamic system. By assigning a set of predefined expectations (variables), you help remove some of the blind spots that the community may face if those expectations weren’t defined. Calling them initial conditions also acknowledges that they may change over time, which is perfectly fine.

A cool conclusion to that effort is that the lab has collectively produced a draft describing the roles and responsibilities of the lab director (Jake) and lab members. It will be fun to check in and see how it’s going as new lab members come in.

Aside: There is a greater than zero chance I’ll end up noting this as an example when writing up my answer to the current WP governance question. This is not that post, though it may seem like it by the end.

Where do you look when you walk into a space for the very first time?

When I first read Jake’s post, I was stuck on that first line. It caught me as a concrete question about actually walking into physical spaces and immediately reminded me that earlier that morning I had stumbled on a post I wrote 8 years ago, Notes From An Essay – “Wonderlust”.

This post is a semi-review of a Tony Hiss essay, Wonderlust, from 2010 that deals with a concept of “Deep Travel”. At the time we were in the process of selling all of our stuff and were getting ready to depart on some long travel. Everything in that essay connected quickly for me.

Reading back, I still really enjoy this:

Some people know a great deal about the stars, others next to nothing. There is always more to find out. But habituation—not noticing something that seems unchanging and harmless—can cloak both knowledge and ignorance with the same mantle of indifference: “Oh, yes, the stars.” Something we have a word for.

Tony Hiss, Wonderlust

There is always more to find out. Always more to observe. And just because we do something some way, doesn’t mean we know why we do it or that it makes sense to continue.

Of course there’s more.

I opened my feed reader this afternoon to catch up on a few things and a post from Jason Kottke earlier in the week titled “The Art of Noticing” caught my eye. Kottke introduces Robert Walker’s book of the same name, self described as a “practical guide to becoming a better observer”.

That post has a couple interesting bits in the context of this one, or at least that’s what I’ve led myself to believe. I’ll quote two of Kottke’s related observations here that I think help tie all of this together into the reason I wrote this post.

Isaacson argues that Leonardo’s observational powers were not innate and that with sufficient practice, we can all observe as he did. People talk in a precious way about genius, creativity, and curiosity as superpowers that people are born with but noticing is a more humble pursuit. Noticing is something we can all do.

And then.

They are literally at a different level in the world, ocularly speaking, and so notice different things. They’ve also got Beginner’s Minds, again literally. Having been a designer for many years, I am pretty good at observation, but my kids are always noticing details that I miss.

Noticing and observing are things that we can all do and can all work to do better.

Documenting the collective observations of a community can help new members avoid blind spots and give them a direct path to contribution.

Having new members in a community (Beginner’s Minds) document their observations can help to evolve the collective observations of that community to further avoid blind spots.

Repeat. 🍻