deon VS Azul

When reading the file, the environment variables will be obtained from the URL and populate the environment.

This is what I had in mind when designing the import functionality for deon [1].

Being able to import also makes it easy to have a .base, a .production, a .local setup, and combine them accordingly.

[1] https://github.com/plurid/deon

Hence the second sentence "[b]ut maybe you don't even need to build another Chromium." and then the second paragraph "cost-reducing" billions to millions day-dreaming of a specification-based pixel generator.

Of course, the n-th time is cheaper, easier, faster, case in point: I implemented 'deon', a notation format for structured data [1], using your amazing "Crafting Interpreters" for which I paid nothing since I was reading the web version as you were writing. Never had the chance to say thank you, somewhere in my drafts there is an email of appreciation: reading your book and applying it chapter by chapter, crafting a final, useful artifact, has been a beautiful experience, thank you very much, for all your writing, since I am a longtime reader of your technical and otherwise texts.

[1] https://github.com/plurid/deon

Not sure what you mean but WebRender powers Firefox which definitely works on the desktop.

You can use it to build desktop UI frameworks - see for example https://azul.rs/

I'd been wanting to see this, preferably with JS being optional, and just allowing direct DOM access.

I initially thought this was what Azul was, but it's only just using Servo's WebRender compositor, and rolls its own CSS parser, DOM, and layout engine, so it doesn't benefit from most of the work done on Servo, and supports less CSS features.

https://github.com/fschutt/azul

Both Servo and Fifefox make use of webrender, which is an awesome piece of tech and is well suited to render a web page. Some GUI projects attempted to use webrender directly as well, like Azul and moxie-native

> But no one is saying, "Hey I have a CSS 2.1 compliant rasterizer and compositor that you can use in your C++ or Rust environment!" are they?

There’s actually quite a lot of interesting work going on in that general space, has been in various forms for some years. A couple that immediately spring to mind:

• Azul <https://azul.rs/> builds on WebRender, as used in Firefox. I haven’t looked at it for a few years, but it looks to have grown quite interesting now.

• Blitz <https://github.com/DioxusLabs/blitz> is based on from-scratch implementations of CSS layout and rendering, and wgpu rendering. It’s not usable yet, but is a very interesting concept. If one happens to be familiar with React Native: it’s kinda like that, or React Native Web.

Azul[1] was my solution for that, it was based on WebRender. I didn't get around to finish it in 2019, but I will work on it this year, maybe I'll get it to be mature enough to post it here.

> wide portability (at least Windoze, Linux, MacOS, iOS, Android, embedded: Azul is Windows-Linux-Mac only, don't underestimate the effort to properly port something to a new platform

> "though a Vulkan-based renderer can be made to run pretty much anywhere": WebRender is OpenGL + using software rendering as a fallback

> a permissive open source license: MPL-2.0

> a C interface/wrap to allow a wide programming language binding support: yes

> and an easily extensible and themable set of basic widgets: also yes

[1] https://azul.rs/

There is Iced which is used by system76 in Pop!_OS, Druid [DISCONTINUED], GTK-rs, Relm, Azul and Tauri. Personally I would use Tauri for its speed using the OS's native web render, documentation of use with things such as Sveltekit and the ability to make UI's using JS, CSS and HTML. Tauri similarly to Electron whilst being far faster. But its up to personal preference really. There aren't any solid "go to" options at the moment.

Sounds like you may be interested in azul not exactly servo based but on projects that originate from servo. Also this is not a typical WebView, for example it does not use HTML but uses DOM to define it's UI, and there is no JS engine in there.

Azul uses webrender. But your "glue" program is like half the web browser. You also need a vector graphics library to render websites. Webrender only does boxes, but not complex SVG paths. Once the plan was to use pathfinder, but mozilla fired the dev and they still using an old version of chromium's skia for that.

One day I'll get around to finish my library Azul [1]. Hopefully.

[1] https://azul.rs/

azul