this post was submitted on 18 Sep 2024
859 points (90.0% liked)
Microblog Memes
5392 readers
4769 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:
- !whitepeopletwitter@sh.itjust.works
- !best_of_mastodon@sh.itjust.works
- !curatedtwitter@sh.itjust.works
- !curatedtumblr@sh.itjust.works
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
What would it actually take? Google did it. Apple did it with WebKit.
Do you have to be as big as google, apple, or microsoft to make a browser? Is a browser as labor intensive as a whole-ass operating system? Or does it have to do with proprietary/patented tech roadblocks?
Please remember that Webkit is based on KHTML, the browsing engine that Konqueror, the webbrowser in the KDE suite, used.
So Apple forked KHTML, made WebKit, Safari, Chrome and loads of other browsers used it and improved it, then Google forked WebKit, and made Blink, their current browsing engine
You could technically fork Blink but the question is whether you have the resources to keep up with web standards. The Web is effectively the universal UI toolkit these days and the pace of development reflects that.
Why fork? Aren’t all of the major engines open source? People can choose one and build a browser around it and leave out the cruft.
You'd need to fork if you decided that you don't like the direction an engine is moving towards. Other than that there's no real reason.