[Overdr0ne]

I really want my tabs to just be emacs buffers.

Emacs has sooo many different tools to organize and operate on buffers, so different types of users can compose a workflow that works for them, including plain old tabs if they really want. And of course, extensibility, the most important feature imo

And you can do this now of course, with w3m or other plaintext browsers, but it's just not that comfy for most webpages these days. And there's emacs-webkit, but it's still a bit of a pita to install.

I still use qutebrowser for most things, and with i3/sway plus the save-session function, i can get hierarchy and persistence, and that seems sufficient for now...

[narwally]

I find that the more you use emacs the more you get frustrated that nothing else works the way it does in emacs. You either deal with it, try and hack some emacs functionality into your favorite tools, or end up living full-time inside of emacs--relegating your desktop environment to a glorified emacs launcher.

[Overdr0ne]

For the record though, I'm very pleased to see people explicitly questioning the UI status quo, esp one so widely assumed as tabs. It seems browsers are just following the 'dont touch anything or you'll drive away our base' method of development, and it's depressing... Can't be much fun for the developers either I imagine. I look forward to seeing what they come up with