So now you're wasting your time doing more work on *packaging* while you were promised *less* work in that area. And it distracts you from improving the application which would bring actual benefits to your users. Even from a security perspective. Should I spend my limited time tightening a Snap/Flatpak sandbox or fuzzing my code? I'd pick the second option *any time*. 13/14
Notices by Gabriele Svelto (gabrielesvelto@fosstodon.org), page 4
-
Embed this notice
Gabriele Svelto (gabrielesvelto@fosstodon.org)'s status on Tuesday, 07-Mar-2023 22:27:59 JST Gabriele Svelto
-
Embed this notice
Gabriele Svelto (gabrielesvelto@fosstodon.org)'s status on Tuesday, 07-Mar-2023 22:27:58 JST Gabriele Svelto
To recap and conclude: both formats end up generating more work for developers, not less, provide little benefits to the users - but very tangible drawbacks - and can't even honor the promise of a single package that can be shipped anywhere.
I could go on for longer, mention how you're better of with something like Electron anyway if you're also shipping on other platforms but this thread is long enough... and I need to fix a Snap-specific bug. End of r̶a̶n̶t̶ thread 14/14
-
Embed this notice
Gabriele Svelto (gabrielesvelto@fosstodon.org)'s status on Wednesday, 23-Nov-2022 04:58:08 JST Gabriele Svelto
The effort at Mozilla to rewrite our crash infrastructure in #Rust yielded a number of excellent tools several of which were not written by us, but by other companies and individuals. Check them out:
* full crash handling & report generation in client programs: https://github.com/EmbarkStudios/crash-handling
* crash processing and analysis: https://github.com/rust-minidump/rust-minidump
* minidump generation https://github.com/rust-minidump/minidump-writer
* debuginfo dumping: https://github.com/mozilla/dump_syms/