Electron clients cannot compete on deep technically obscure feature sets, simply because they didn't have 20 years to accumulate them. They cannot compete on latency. Thunderbird should remain native.
Electron clients cannot compete on deep technically obscure feature sets, simply because they didn't have 20 years to accumulate them. They cannot compete on latency. Thunderbird should remain native.
Er, you do realise that Thunderbird isn't exactly native, either, what with it being based on XUL (or whatever's still left of that these days) and Gecko?
Something that competes with electron is not electron. Non-native includes RLBox which is now going to secure Firefox according to Mozilla. Mozilla is on record regretting thunderbird's poor Integration with the Firefox stack as a trial for thunderbird devs and a tax slowing Firefox engineering.
This holding pattern has gone on and on because no one wants to establish the correct API layer to maintain as an inherent tax for Firefox engineering that enables all F/OSS to reuse the NS* stack correctly with good documentation.
In the long term this means chromium has an ecosystem and Mozilla's stable ecosystem consists of just one browser. However flawed chromium is, it has no competition for most developers and competition with WebKit for a handful.