90% of the functionality is written in rust components and the UI is a very slim wrapper around those APIs; it seems.

And even then it looks like the JS is WASM compiled from rust.

It’s not implemented in JavaScript/typescript is what I mean. As such it seems to be lean on my system.

If it is Electron, I don't think you can credibly call an entire Chromium instance a "very slim wrapper".

There's a chance it's using Tauri (rust) https://tauri.studio/en/ if it's truly not using Electron but a similar concept. However WASM builds in Electron would make more sense if they use the term Electron.

No, it's definitely regular Electron:

    % tar ztf 1password-latest.tar.gz | grep "chrome"
    1password-8.1.1.x64/chrome-sandbox
    1password-8.1.1.x64/chrome_100_percent.pak
    1password-8.1.1.x64/chrome_200_percent.pak

yeah I'm aware it contains chrome, I mentioned that much of the functionality has been moved out and is actually implemented in rust, this is verifiable simply by running `1password --log trace`

EDIT: 168MiB resident memory on my system (just checked).

Though it malloc'd (but never used) 32G, that's worrying.

Link below to the behind-the-scenes article. I have no experience using the Linux app so I'm not sure of the performance but a lot of the core seems to be written in Rust compiled to WASM which is the way it's now being done for their browser extension. Personally everyone keeps cribbing about electron but I hope 1Password has found a way to make good on performance

https://dteare.medium.com/behind-the-scenes-of-1password-for...