- cross-posted to:
- sandrolinux
- opensource
- firefox
- cross-posted to:
- sandrolinux
- opensource
- firefox
New gecko based browsers are rare nowadays but this one is especially unique to me because it is more than just “firefox with tweaks” like a lot of the ones I’ve come across. The UI is different, it’s working on custom settings, a new more powerful sidebar, a new theming system, and potentially IPFS/Dat support further down the line. It’s very early in development but it’s still impressive as it is.
Error, no FUD, nothing more than entering in the Mozilla page, they give you an Alphabet Inc tracker, among others, if you do not block it. Mozilla has economic relationship with Google, as is easily verifiable.
so what browser do you use? like @SeerLite@lemmy.ml said Mozilla Firefox is about as removed from google as you can get while still using web this side of the millennium.
Simple! Get a Mac and use Safari. Mac is certified Unix so it’s way better than that knockoff Linux! /s
Safari is using blink, google’s web engine. The only alternative is Mozilla’s Gecko. So we must support it. I hope that there was more alternative because I believe in web engine freedom, but rn our only option is Firefox.
Safari uses webkit unless they changed something big recently, but since blink is a fork of webkit it’s still very similar compared to firefox and gecko.
Blink isn’t a fork of WebKit, it’s a improvement of WebKit, like WebKit is a improvement of KHTML from KDE. Gecko was a trademark of Netscape, first called NGLayout and was adopted by Mozilla in 1998 until today. The underlying problem is that there has not been a development of a new engine for 20 years and all the ones that were there have fallen by the wayside, because they cannot adapt to new web formats. The only ones left, aside from some rudimentary engines in the Text Browsers, are Blink, Gecko, and perhaps a while longer WebKit, before becoming completely obsolete. Safari is already in the benchmarks in performance and compatibility with IE.
Webkit uses blink
???, no, what’s more, Apple requires browser developers to use WebKit in order to be included in the Apple repository. This is why many browser developers who use Blink or Gecko have a lot of difficulties to change their browser for Apple. Apple does not want to lose its monopoly of Safari on its platform, a practice that will cost them dearly sooner or later, as it is a very limited platform in functionality.
You’re right, Apple requires browser to use WebKit on their platform.
What I said tho, is that WebKit takes a lot of their code from blink. Blink was created as a WebKit fork. As you probably know, maintaining a modern web engine requires a lot of effort. What WebKit does to keep itself updated is to get the code from Blink removing chromium specific parts. So at the end, WebKit is only a reduced version of chromium.
deleted by creator
Well, more or less, but this practice can be carried on for a season. If Apple does not want to stay on the road, it has to get off the podestal and once and for all accept that WebKit has its limitations, no matter how much they patch it. As I said before, until the old IE almost equals in performance with Safari, while developers look black trying to get a browser for iOS that has a minimum of functionality. Vivaldi’s small team has been trying for several years to get an iOS browser out of the alpha phase, because many of its functionalities do not work in WebKit. Not for nothing has WebKit been forked and improved to create Blink, this work, due to the complexity of a render engine, nobody does, if it was not necessary already at that time. But Apple is Apple, more important design than functionality, design can be charged more expensive.
How much do the wheels of your car cost?