simple-tab-groups VS ladybird

The older release is still available on that page, but presumably with different features. Development looks very active here: https://github.com/Drive4ik/simple-tab-groups/tree/master/plugins/stg-plugin-group-notes

Please use this page to report issues with Simple Tab Groups.

You can use this page to ask questions or submit your feedback about Simple Tab Groups.

Please open this page and click on New issue to contact the people who created Simple Tab Groups.

Are there reasons that the "Simple Tab Groups" extension isn't suitable for you? It seems to be well-maintained, cleverly uses Firefox's "hide tabs" API to keep a single window behind-the-scenes, and has integration with lots of other features like Firefox's containers. I think it's an indirect descendent of the old Tab Groups extension when it was spun out of Firefox.

https://github.com/drive4ik/simple-tab-groups

Just use Simple Tab Groups honestly

I assume that the speed is partly a consequence of not integrating with the context menu items of other extensions and of Firefox. See for example the discussions at and around https://github.com/Drive4ik/simple-tab-groups/issues/749#issuecomment-783171538

tab grouping extensions that do not misuse Firefox containers were developed, however in the absence of a tab groups API, conflicts are inevitable

A browser is not a web app, it doesn't have a strict separation of "frontend" and "backend" in the same sense that a web app would have; the lines are drawn quite differently. The rendering engine is never "just" the rendering engine; you can't abstract or swap it without tremendous effort.

If you'd like to learn more about how a web browser project would organize its internal architecture, but are discouraged by the complexity of Chromium, Firefox, etc. I'd recommend source diving Ladybird (https://github.com/SerenityOS/ladybird), NetSurf (https://www.netsurf-browser.org/), or Dillo (https://www.dillo.org/).

I'd love to see a stable version of a brand new web browser, not based on Blink or Gecko, such as Ladybird or Flow Browser. Competition is a good thing.

note, native Windows is not currently supported:

https://github.com/SerenityOS/ladybird/issues/113

Google is dominating, pushing through Android and via Googles-Webservices and Microsoft is using it now. A reason to worry because developing new web-engine requires an big effort. For instance Microsoft only allows usage of Microsoft Teams Web with a webbrowser based upon Blink. So were back in 2002?

WebKit features also WebKit2Gtk (Epiphany) and Qt5-webkit (Otter) with native integration. They use the native toolkits, which is an advantage! Interaction with the open-source community around WebKit seems rather good and the engine is integrated by others. Gecko seem not to be integrated by others, but by forks only? You remember when Chrome was considered slick and fast? Originally Google used the native toolkit on every platform but know they use an own solution on every platform, like Firefox.

Maybe there is a new kid on the block:

https://github.com/SerenityOS/ladybird

Funny you should ask: https://github.com/SerenityOS/ladybird

I've not heard of Ladybird before. True, it's a free and open browser engine and a very interesting project!