51–60 of 93 posts
See also Ladybird for another from-scratch browser being built by a more ragtag indie group. https://ladybird.dev/ The chaddest of the chad projects honestly.
Why do we need another browser engine written in C++?
Earlier quoted context omitted.
> 1) there's probably a niche to be filled by an OSS browser engine focussed on embedability Absolutely. Electron or something Electron-like with Servo embedded could be a nice outcome. Tauri already fills that niche a bit, but uses whatever the OS provides, rather than embedding anything. Would be nice with something in-between that.
Tauri is actually adding experimental Servo support.
Earlier quoted context omitted.
> Can't believe Mozilla wasn't interested in it The fact that mozilla wasn’t interested in that really tells a lot about their priorities
They fired everyone working on it and completely abandoned it while giving the CEO a million dollar pay raise the same year. When are we going to talk about how openly corrupt Mozilla has become? They clearly have issues at the top that need to be fixed for the betterment of web.
Now: I agree that the pay is absurd! I'm quite willing to believe she's not worth it, too. But she's hardly the first CEO to have ridiculous pay; nor am I convinced the board is overcompensating her for corrupt reasons - it may simply be a difference of perspective. And - perhaps I'm wrong, and this pay is a going market rate and a hypothetical cheaper replacement would do worse - I really don't believe that, but to call something corruption I'd need to be rather sure of that and of their knowledge of it.
I'm very excited about Servo. Can't believe Mozilla wasn't interested in it. Not only the idea of an engine with great security and performance is an excellent one, but I also love the idea of a web engine as a component. This for some reason seems to have disappeared in modern times. IE used to have an ActiveX control back in the Windows 9x days. You could embed a web engine anywhere you wanted. KHTML also worked li…
sorry, too many questions perhaps.
Earlier quoted context omitted.
> Can't believe Mozilla wasn't interested in it The fact that mozilla wasn’t interested in that really tells a lot about their priorities
Or they (Firefox folks) learned what happens when you (Netscape) try a major greenfield rewrite (Netscape v5) so ambitious that it becomes the example of why one should never rewrite. And instead just back ported the lessons learned to make Firefox/Gecko better years earlier than a rewrite could.
And it really doesn’t matter whst conventional wisdom holds, when the architecture of a project is based on flawed assumptions, or things just changed since it was architected.
It has to be majorly refactored, period.
I'm very excited about Servo. Can't believe Mozilla wasn't interested in it. Not only the idea of an engine with great security and performance is an excellent one, but I also love the idea of a web engine as a component. This for some reason seems to have disappeared in modern times. IE used to have an ActiveX control back in the Windows 9x days. You could embed a web engine anywhere you wanted. KHTML also worked li…
It seems I'm utterly and entirely misled to believe that Servo is the engine behind Mozilla since... FF52 (it was, right)? Can some please explain what is it that Mozilla uses then to render pages, and which parts did Mozilla rewrite in FF? Did some parts of Servo made it into FF, and is FF contributing back to Servo? sorry, too many questions perhaps.
I'm very excited about Servo. Can't believe Mozilla wasn't interested in it. Not only the idea of an engine with great security and performance is an excellent one, but I also love the idea of a web engine as a component. This for some reason seems to have disappeared in modern times. IE used to have an ActiveX control back in the Windows 9x days. You could embed a web engine anywhere you wanted. KHTML also worked li…
WebKit is still very embedding-friendly, though building it on Windows is messy. Works great under macOS and Linux though. We absolutely need more embeddable web engines though. Gecko is nice but it being permanently joined at the hip with XULRunner is killing it.
XULRunner's last release was off of the 41 branch, 8 years ago. It's dead.
I'm very excited about Servo. Can't believe Mozilla wasn't interested in it. Not only the idea of an engine with great security and performance is an excellent one, but I also love the idea of a web engine as a component. This for some reason seems to have disappeared in modern times. IE used to have an ActiveX control back in the Windows 9x days. You could embed a web engine anywhere you wanted. KHTML also worked li…
I have used CEF, WebKit, and WebView2. Only the former is easily embeddable cross platform, and as soon as it became popular, Google put a lot of resources into disallowing Google login from it or any other embedded browser[0]. I had to abandon my own CEF-based browser because of this. While I abhor the business practice, there's nothing I can do. If my browser can't login to Google products, it can't see much adoption and I don't have the time to try and win a cat-and-mouse game against their detection methods.
If we want embedded browser components to be more mainstream where anyone can develop a browser, we're going to first have to address that large companies block them if they get too popular but the embedding company is not popular. Ideally an embeddable non-Android Gecko would come about because FF is too big to block (lots of talk in the past, and I even PoC'd stealing the window handle[1]). But there's no money in it.
0 - https://developers.googleblog.com/2016/08/modernizing-oauth-...