4 ms·
This is really cool but I can’t say I’m a fan of Zapium given it would move to a commercial license in the future. If you have to ship CEF anyhow, what is the p
by priansh 4y ago
This is really cool but I can’t say I’m a fan of Zapium given it would move to a commercial license in the future. If you have to ship CEF anyhow, what is the performance advantage to licensing and using Zapium over just compiling WASM and shipping binaries with Electron? FWIW — this is how Java, .NET, etc packaging is done for interop with Electron.
I can understand from an ease of use perspective to have the bridge in between but it wouldn’t be worth subjecting a codebase to commercial licensing IMO. It’s not a whole lot more work to use process calls instead there so it seems an odd choice to commercialize that aspect in particular.
- ayanb 4y ago>> this is how Java, .NET, etc packaging is done for interop with Electron not certain if this should be the status quo for the longer term.
- heavyset_go 4y agoWhat's Zapium? I searched for it, but nothing relevant came up.
- price 4y agoLooks to be this: https://zaplib.com/docs/zapium.html https://zaplib.com/docs/zapium.html > Zapium is the native, cross-platform Zaplib runtime. It converts Zaplib web apps to desktop apps, where the Rust code runs natively, not via WebAssembly. > This is Zaplib's equivalent of Electron -- for an extra speed boost.
- deleted 4y ago[deleted]
- heavyset_go 4y agoThanks