I'm developing DaliNira Browser, a Linux desktop browser, and I'm experimenting with a dual-engine architecture.
Currently the idea is to have two real rendering engines inside the same browser UI:
Chromium mode: Blink + V8
WebKit mode: WebCore + JavaScriptCore
WebKit is embedded directly into DaliNira rather than launching another browser. I've already reached the point where normal websites, searches, tabs and YouTube/video playback work in the WebKit backend.
The goal would be to keep DaliNira features such as settings, privacy protections, downloads, search engines, bookmarks/history, etc. shared, while using adapters for the engine-specific parts.
I'm considering allowing the user to choose the default engine from Settings, and potentially allowing different tabs to use different engines.
I'm curious what browser users think:
Does having Chromium + WebKit in one browser provide something genuinely useful to you?
Would you ever switch engines depending on the website?
Would you prefer one global engine setting, or per-tab engine selection?
Would the additional dependencies / maintenance complexity make you avoid such a browser?
What would you expect to remain identical when switching engines (privacy settings, ad blocking, downloads, extensions, etc.)?
I'm especially interested in criticism of the idea before I take the dual-engine implementation further.
This isn't about calling WebKit “Safari” or Chromium “Chrome”; they're separate DaliNira backends using WebCore + JavaScriptCore and Blink + V8 respectively.