I was referring to a choice between WebKit and Chromium/Blink in Otter, not the web in general, though the sheer resources required to keep up with the Web(R) from other players may be leading us that way (hopefully not).

For example, after switching the preferred engine in about:config, it's even possible to leave Otter in a transitional state, having one tab load a web page in WebKit, and another in Blink, in the same running application.

And it's quite good. I switched over a little over a year ago, and I have no regrets.