Admittedly my source is the Ubuntu podcast, and it would probably take me awhile to find the exact quote, but according to the employees, they previously had one or two employees whose full time job was simply maintaining the Chromium deb package. Switching to snaps made it much easier and freed them up to do other things.
I think we should consider snaps like any other framework, be it deb, flatpak, or even something like Electron: some of them have serious downsides, but people choose them because it allows them to more easily push a single binary out to multiple platforms rather than being bogged down in maintaining a distinct build procedure for Windows/Mac/Deb-based/RPM-based/Arch/Solus/every other percent-of-a-percent Linux distro.
I don't like snaps either--I much prefer flatpaks. But I don't think it's constructive to insult Canonical employees for wanting to make their own jobs easier while they work to provide you a free product.
I think we should consider snaps like any other framework, be it deb, flatpak, or even something like Electron: some of them have serious downsides, but people choose them because it allows them to more easily push a single binary out to multiple platforms rather than being bogged down in maintaining a distinct build procedure for Windows/Mac/Deb-based/RPM-based/Arch/Solus/every other percent-of-a-percent Linux distro.
I don't like snaps either--I much prefer flatpaks. But I don't think it's constructive to insult Canonical employees for wanting to make their own jobs easier while they work to provide you a free product.