this post was submitted on 23 Apr 2025
1144 points (98.3% liked)
Microblog Memes
7465 readers
2642 users here now
A place to share screenshots of Microblog posts, whether from Mastodon, tumblr, ~~Twitter~~ X, KBin, Threads or elsewhere.
Created as an evolution of White People Twitter and other tweet-capture subreddits.
Rules:
- Please put at least one word relevant to the post in the post title.
- Be nice.
- No advertising, brand promotion or guerilla marketing.
- Posters are encouraged to link to the toot or tweet etc in the description of posts.
Related communities:
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
That is mostly but not entirely true, Firefox has a few variants of its own, alternatives do exist.
I did some research into the topic not long ago, you basically want to choose an engine and from that a browser
Gecko basd (Firefox)
Goanna based (Fork of Gecko)
Servo based (very early in development/not for daily use)
Ladybird: fully independent engine and browser
Also waterfox. Can't forget about waterfox. That said, I'm daily driving Zen at this point and am extremely happy with it
Also for completion of the taxonomical reference above, Safari GNOME Web and Konqueror use the actual WebKit rendering engine that branched from KDE Plasma in 2001.
Chrome, Edge, and all the Chromium-based browsers use “Blink,” which branched from the WebKit project in 2013 and evolved separately. It’s different enough now to be considered distinct (developers supporting these browsers need no reminder) but a portion of the original properties are still shared.
Most of the time when people say “webkit” they’re referring to Google’s Blink engine, but the original WebKit project is still around and lives on in a handful of evergreen browsers that bear mention.
Thanks for compiling this so I can reference it later if Firefox ever becomes an issue