Ultralight

Web rendering would be Blink, with V8 being the JavaScript engine. I believe they have their own UI rendering process. I know of another company that does something similar for the UI process, but with WebKit instead as the base: https://github.com/ultralight-ux/ultralight#rocket-dual-high...

I do care, and in your example, it depends on what license the project uses and how "proprietary_library" is distributed. In this specific case, if Muon distributed a copy of Ultralight (which it doesn't seem to; I'm not sure why I'm spending so much time on this), the it could not be GPL'ed, for example, because Ultralight has a proprietary (incompatible) license [2]. For a license like MIT or BSD, I think applying that license is technically valid, but again, not very practical. I doubt Muon would make it into the OpenBSD repos, for example. Its distribution is hindered by the depedency. Basically, "open source" doesn't really mean anything in this context; you need to consider specific licenses and circumstances. [1] https://github.com/ImVexed/muon/tree/master/ultralight [2] https://github.com/ultralight-ux/Ultralight/blob/master/lice.

The list of missing features [1] makes it clear that this is unusable for any realistic desktop app. No local file selection, no platform drag-and-drop… no CSS filters for UI effects, even. Nowhere near production ready. [1] https://github.com/ultralight-ux/Ultralight/issues/178

There seems to be a fair amount of missing features too https://github.com/ultralight-ux/Ultralight/issues/178

There are game-tailored browsers like Ultralight (https://github.com/ultralight-ux/ultralight) but they generally assume that they're only hosting the user interface, not the entire game. I suspect that the major hurdle stopping "Electron for game consoles" is that the console SDKs are under NDAs - you'd have to verify that the users are registered console developers or provide a porting service yourself (as many porting houses do). However, Microsoft do allow packaging HTML5/JS games as UWP apps, and testing them on the Xbox Series (and the Xbox One) with the Dev Mode: https://docs.microsoft.com/en-us/windows/uwp/xbox-apps/devel...

A step towards the right direction, I am curious how it performs in relation to Ultralight[0]! [0]: https://github.com/ultralight-ux/Ultralight

According to the Architecture section of the GitHub page [1]: > Ultralight is a new port of WebKit combined with a new [proprietary] lightweight renderer intended specifically for embedding in apps and games. And the Licensing section: > Ultralight is free for non-commercial use and free for commercial use by companies with less than $100K gross annual revenue. For more info see LICENSE.txt Pricing [2] is available from the main web site. [1] https://github.com/ultralight-ux/Ultralight#architecture [2] https://ultralig.ht/#pricing

> There are some drawbacks such as Windows edition is based on IE etc. Well that's kind of a non-starter. Part of the appeal with shipping an entire browser in an Electron app is to give yourself a fixed target. It always seems that these "Electron killers" all have some fatal flaw, be it "just use whatever the system browser is" or "just as good as Electron, if you don't care about file drag-and-drop, system clipboard integration, full CSS support, minor things like that"[1]. 1: https://github.com/ultralight-ux/Ultralight/issues/178

Interesting, it's not too farfetched of an idea since there is a C++ API for accessing the DOM in WebCore and we have the ability to disable JS completely. I've added this to the issue tracker as an idea to explore. [1] [1] - https://github.com/ultralight-ux/ultralight/issues/14

Hi there: Pros (Ultralight is...) - Smaller distributable (25% the size of Electron/CEF or smaller). - Simpler and easier to build (fewer dependencies and smaller codebase). - More configurable (users can do custom handling of file system, fonts, GPU rendering, clipboard, and more). - Potentially more performant (all rendering is done via GPU command buffers). - First-class support from an actual company. Cons: - No support for MathML, Geolocation, WebGL, IndexedDB, WebAudio/Video (for now) - Less mature and unstable. - Slower release cycle (might be a pro). Linux support is planned and will ship when it's ready, you can track its progress here: [1] Yes, we have plans to publish a C API interface to simplify bindings for other languages. The WebCore source is available here [2]. The rest of the source is kept closed for now to keep our li