Bring them 10 clients with 100K+ paid support systems each who won't sign the contract without a non-snap chromium packing solution. But I seriously doubt that Canonical is packaging Chromium. I think the google Chromium team is behind it.
Canonical is a business. Money talks.
Snap deployments are strategic goals for Canonical, so by necessity, they may not entertain any other option for a number of years.
In the meantime, you do know that we can run the version of chromium contained inside the snap package, but without the snap confinement or settings, right?
Code:
$ more ~/bin/chromium.sh
#!/bin/bash
/snap/chromium/current/usr/lib/chromium-browser/chrome $* &
Unfortunately, chromium internal code is blocking the use of my preferred sandbox, firejail. I haven't done the research to figure out the new firejail profile settings needed for chromium as provided by the snap package, to work. There is still a chromium for 16.04 that doesn't use a snap and it runs fine inside a firejail.
Bookmarks