The work behind
the SDK.
Attar’s first commit landed on 23 July 2026. Eight weeks later, the work spans a compiler, a browser-engine fork and native application tooling. Here is what that work involves.
- Chromium patches
- 770
- Hermes patches
- 43
- Weeks since the first commit
- 8
Ordered source series in the reviewed snapshot. These counts describe engineering work, not supported features. Counting method ↓
Make a browser engine
serve one application.
Blink already implements the DOM, CSS cascade, layout, text and painting. Attar keeps that work. It changes how the engine is built and embedded so a native application can use it without shipping the whole browser.
That means working inside Chromium: native windows, input, accessibility, resource loading and presentation all have to remain connected. Removing a subsystem is useful only if the application still behaves correctly.
Reuse the web engine
Blink for web semantics. Chromium’s rendering and platform code for the native interface.
Compile the application
Ahead-of-time JavaScript and a fixed executable graph, linked with the engine code the application needs.
Two substantial upstreams.
Attar maintains changes to Chromium and Meta’s Hermes. Chromium supplies the UI engine; the Static Hermes fork supplies JavaScript compilation and execution. Their responsibilities stay separate.
| Upstream | What Attar changes | Patches |
|---|---|---|
| Chromium | Native UI embedding, retained web behavior and the application’s engine closure. | 770 |
| Hermes | Ahead-of-time compilation, the compiled runtime and native embedding boundaries. | 43 |
Ordered patch series record those changes against pinned upstream sources. They make the fork reconstructible and give each update a concrete set of changes to review.
Rust connects the platform, application lifetime and public native interfaces. The C ABI also lets other native code meet the UI at the same boundary.
A build is only one check.
Compiler tests check language behavior. Native tests exercise the retained engine interfaces. Packaged application checks cover another level: startup, rendering, interactions and teardown.
Those results answer different questions. The JavaScript report and web-platform report retain passing, failing and unmeasured results. A source audit or successful bundle is not a substitute for a native application run.
One concrete research result
The recorded Etcher comparison shows the direction: the same application occupied 375.1 MiB with Electron and 73.3 MiB in the Attar build. The full comparison gives the machine, methods and other measurements.
That work belongs to Attar Electron R&D. Attar Electron is planned and is not included in the standalone SDK release.
Count the series,
keep the scope.
The Chromium total comes from the reviewed export manifest: each of its 770 patch entries matches its recorded SHA-256. The Hermes total counts the 43 entries in its ordered series. Loose patch files and legacy queues are excluded.
The snapshot was reviewed on 2026-09-17. Eight weeks means 56 calendar days since the first commit, not eight weeks of one person’s effort. These are source counts, separate from release compatibility.
The current SDK guide describes what developers can use. Additional frameworks and the Electron compatibility layer have their own place on the roadmap.