Riiiiichard

Thanks, that's really useful coming from someone shipping CEF in production, and ZShot looks great.

And you pointed a real gap: the release archives contain no license or notice files, I will add them in next release. Thank you!

Where zebkit easier thane CEF: 1. setup: cargo add zebkit for rust, pip install zebkit for python. Golang bindings is planned 2. your event loop 3. a plain C api with rust, python, and node-free js bindings on the top 4. offscreen rendering 6. batteries: PDFium API, 7000+ API from chroium's or its dependencies 7. automation: playwright api in native with no cdp and node required 8. size: well, smaller but not much (1/3 smaller than latest electron, measured on linux)

Where CEF is still ahead: 1. Maturity: it's a product over decade and a big community, zebkit is rather young, but I will keep maintain it 2. platform: zebkit ships linux x64, macos sillicon and windows x64, cef covers mac intels, arm linux and many others. 3. missing pieces: zebkit has no printing, web bluetooth, wideevine and so on

Zebkit is still a young project, and I’d love to hear your feedback to help it keep improving.

I agree with you on the core point: the same layer (zebkit embeds chromium using Content API), staying sync with upstream (it carries 60+ patches), the size reduce (using build options such as turning off features).

For the size, I have some more to address: the real weight comes from Blink, V8, skia, network stack and media. WebRTC cannot be dropped since Blink depends on it. Video playback is need by most apps so it stays. And the webusb is small, drop it has little benefit.

The main differences are mostly from shape, not the engine: 1. Exposed as a library with bindings (rust, python, JS without node) that can be run in your application's own event loop 2. Almost everything in the engine have a hook point such as permission, network, dialog, menus .. 3. Exported Chromium's C Library (such as boringssl, zstd, ffmpeg ..) for your app so you do not need compile it or ship it twice such as ELectron. 4. Exported feature rich PDF library (pdfium with improved) 5. Playwright inside, no cdp and no node are required

Yes, it has the same process sandbox features like Chromium.

Yes, I'm actively maintain this project, If you want to have go bindings, no problem.

It has the same sandbox support and limitations as Chromium. It supports X11 default in Linux and with limited Wayland support.

It has been tested on M4 macbook and works fine, if you have issues, just post it on the project.

Short version:

It packages Chromium as a library you can embed directly into applications to add browser capabilities.

It’s trimmed down to be 33% smaller than Electron, with native browser automation APIs for AI agents that run 3–10× faster than tools like Playwright operating over CDP. It also directly exposes 7,000+ functions from Chromium’s bundled libraries for your application to use.

ConciseMark is a simplified markdown parsing library written in Rust with customization, math supporting in mind. The simplified here means it only supports some common markdown syntax but not full.

And I also update my nvim-previewer(https://github.com/ikey4u/nvim-previewer) plugin to use concisemark because I want to preview math equation which neither pulldown-cmark nor comrak supports.