[07:57] <tarzeau> https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bugs?field.searchtext=snap&search=Search&field.status%3Alist=NEW&field.status%3Alist=INCOMPLETE_WITH_RESPONSE&field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE&field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.status%3Alist=FIXCOMMITTED&field.assignee=&field.bug_reporter=&field.omit_dupes=on&field.has_p
[07:58] <tarzeau> atch=&field.has_no_package=
[07:58] <tarzeau> i really wonder why ubuntu forces users into snap
[07:58] <tarzeau> and if 20.04 will be so as well or not
[08:03] <lotuspsychje> tarzeau: i think that will depend how much user oppose to it
[08:04] <lotuspsychje> tarzeau: think in this stage, all we can do is file alot of bugs
[08:36] <tarzeau> i'm testing building chromium-browser backports from debian...
[08:36] <tarzeau> and we just had weekly meeting, considering like google, switch to debian
[08:49] <TJ-> tarzeau: I think the rationale for a lot of the snap packaging (by Canonical) is to make rolling release style for rapidly changing projects less of a headache to manage - which in the regular release process would be constant SRUs and/or backports
[08:51] <tarzeau> i don't want rolling release for rapidly changing projects. and that'd be possible with deb packages perfectly fine too
[08:53] <tarzeau> once i'm done with pip2/python2 removal, i'm certainly not adding snap. i'll get rid of pip and snap both at the same time, by 20.04. and building chromium-browser is PITA, so it'll be no option to create an autobuild. much easier to just switch to debian again (we had it for years after all)
[08:53] <tarzeau> unity was the only reason (among nvidia officiall supporting ubuntu) to have ubuntu
[08:54] <tarzeau> (and oh well the fixed release dates, but fine if i don't have them anymore)
[08:54] <TJ-> tarzeau: rolling release for .deb wouldn't be possible if the package has extensive dependencies on external library versions that keep being changed
[08:55] <tarzeau> TJ-: chromium-browser doesn't. i'm able to do a simple autobackport of chromium-browser (sid) to bionic
[08:56] <tarzeau> i'm more concerned about companies doing this: https://mathpix.com/
[08:56] <tarzeau> provide their software for linux ONLY via snap, no source
[08:57] <TJ-> tarzeau: right, but snap is aimed at more than chromium, I think that was part of the original thinking behind snaps. The major aim being to allow 3rd party developers to easily add proprietary applications 
[08:57] <tarzeau> does matlab, mathematica, maple already exist as snaps?
[08:57] <tarzeau> idl? 
[08:57] <TJ-> I have no idea I don't allow snaps
[08:58] <tarzeau> that's been solved by environment-modules and spack
[08:59] <tarzeau> what is your antispyware measures?
[09:00] <tarzeau> we also have snaps operated away for 18.04 LTS machines
[09:00] <tarzeau> the report back on installation (if you say no, it reports back you want to opt out) the motd reports machine/memory/etc infos