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.
???
Yes, all motors are FOSS, but the update are patches. You can review all the code (script~2Gb for WebKit) and analyse it before you are retired? The updates for this are adons, to patch some security and compatibility holes, not a real improvement, which requires a lot of recources and developers.
Gib source code tracker with releases and real changes
???
For real, I dont know if you are memeing or what. The worse thing is that in WebKit port to GTK they even have a blog in which they speak about the changes in WebKit and is deeply known that there was a big API change and way that the engine works between WebKit 1.x and WebKit 2.x for which they had to adapt the port. And this is just a little thing inside all of this.
Still you say that there are no true releases nor changes. Wtf.
So I don’t understand why Safari and others with WebKit perform so poorly compared to Gecko and Blink.
The first thing is V8 and SpiderMonkey VS JavaScriptCore.
You say it, that Apple will have to use Blink. As I said before, if WebKit had no limitations, no one would have bothered to develop Blink many years ago. Now the developers have enormous difficulties in implementing the functionalities that they have in their corresponding Blink and Gecko browsers, in WebKit so that Apple accepts them.
I never said that WebKit should be replaced by Blink…
No, but nevertheless I think that sooner or later there will be no other than the WebKit browsers going to Blink.