search

OtterBrowser / otter-browser

Otter Browser aims to recreate the best aspects of the classic Opera (12.x) UI using Qt5
https://otter-browser.org
GNU General Public License v3.0
1.83k stars 278 forks source link

Investigate Servo backend #1111

Open Emdek opened 8 years ago

Emdek commented 8 years ago

Since Gecko is currently not embedding friendly and not everybody likes Blink or WebKit, we should investigate if it is possible to create Servo based backend.

pierreporte commented 8 years ago

Will all the work you did for QtWebEngine, which currently uses Blink as backend, be compatible with Servo? If not, it may not be worth it now as there will be a lot more to do and Otter is not yet stable.

Apart from purely technical reasons, the supremacy of Blink and Webkit in the world of rendering engines may cause a big problem in the future (I am not a specialist, but I read that it would cause the same problems as IE6 ten years ago). For this reason, using Servo would be a good choice.

Emdek commented 8 years ago

@pierreporte, since the unstable part is usually something wrong in upstream libraries... ;-) It would be best if such backend would have own maintainer or something like that.

ghost commented 8 years ago

As Mozilla tries so hard to be even more Chrome than Chrome itself, i wonder if Servo will have any future at all.

I would be these days very careful with everything Mozilla related.

zakius commented 8 years ago

I don't know if Mozilla makes even more chrome than chrome, for now firefox is superior to anything released as stable (except dreadfully outdated opera) and I hope it won't chrome itself to the level of being useless (like chrome or chropera)

ghost commented 8 years ago

You have still the benefit to bring back complex customization features with add-ons like Classic theme restorer back, but the features itself are still removed from the browser itself. Just wait until Mozilla kills of XUL and implements the more restrictive Chrome extensions model, that will be the moment where the real "fun" will start. Anyway, until Firefox 22 i would have called Firefox superior, but not anymore these days, if you take a look at the road where Mozilla is driving. But this is off-topic, enough of that :D

Emdek commented 8 years ago

@SJ-Diamond, AFAIK currently Mozilla doesn't plan to replace Gecko by Servo, they want to use some of its component for now only, but only future will tell what they really want to do with it.

zakius commented 8 years ago

AFAIK Mozilla wants to keep as much possibilities in API as possible (...?), but making it trivial to run chromium extensions in firefox (but that itself doesn't mean that firefox extensions will work in chromium as they can use extended API) I agree that they are taking some things away (and the removal of Pocket extension cause they built in "add to pocket button" was plainly dumb) Still it's API allows for much more than anyone, so it is superior, even if goes down with every update there's a long way down to chromium

And Servo seems to be aimed mainly at mobile devices (where it could better utilize multi-threaded optimizations and algorithms, as on desktop and not-so-mobile devices like laptops dual core processors are still pretty common, and mobiles tend to have 4+4 or more), but if it goes well porting it to desktop is likely

s8321414 commented 8 years ago

I think it's a good idea if Servo is considered as stable :smile:

ShalokShalom commented 7 years ago

There is a Servo browser, which renders on OpenGL directly, without any toolkit, the whole UI written in web languages.

mariokamenjak commented 7 years ago

Mozilla will eventually completely remove gecko. It will be a gradual transition though.

ShalokShalom commented 7 years ago

Yeah, I think so too. The nub of the matter is; when becomes Servo useable?

mariokamenjak commented 7 years ago

Their roadmap says that major features of Servo will be in stable Firefox by the end of 2017.

Emdek commented 6 years ago

I'm wondering if this ticket still makes sense, I haven't heard anything new in long time and it seems that Mozilla integrated some features back into Firefox creating memory hungry beast.

Frenzie commented 6 years ago

They way Mozilla marketing has phrased it they've been plugging parts of Servo into Firefox. I don't know. :-)

Emdek commented 6 years ago

@Frenzie, yeah, according to comment above they were supposed to be already done with that integration by now...

ShalokShalom commented 6 years ago

Two seperate projects: Servo and Mozilla. As you see, Servo is its own project: https://github.com/servo/servo

Mozilla decides to integrate parts and supports the project. The own browser/UI is still in development.

See here the current state: https://download.servo.org/

Emdek commented 6 years ago

@ShalokShalom, it seems that it will take some more time before it will be production ready...

ShalokShalom commented 6 years ago

Thanks for the consideration