441–450 of 538 posts
The conversation around snaps starts at 5:20.
It sounded to me that they genuinely tried to put themselves in both side's shoes.
From the linked announcement: https://blog.linuxmint.com/?p=3906 > Applications in this store cannot be patched, or pinned. You can’t audit them, hold them, modify them or even point snap to a different store. You’ve as much empowerment with this as if you were using proprietary software, i.e. none. This is in effect similar to a commercial proprietary solution, but with two major differences: It runs as root, and it…
You absolutely nailed it and this is why -- if I have any say in this (and I do) -- we will be moving away from Ubuntu. It's a completely insane stance for server systems. (I believe it's still possible to run server systems without snaps with various "workarounds" etc, but we can feel which way the wind is blowing...)
Earlier quoted context omitted.
I've been using Pop!_OS on a System76 laptop since February, and like it quite a bit. I use plasma desktop on all of my other systems, but left this one with the defaults.. so far I really like it, but I have a problem with gnome-shell leaking memory over time, since I tend to not shut down or log out over long periods of time. If I don't restart / log out, /usr/bin/gnome-shell eats up more and more memory (as the gd…
Going to fire this up in a VM now and give it a go, maybe replace Ubuntu 20.04 with it. I just tried out Mint but it installs SO much rubbish. It installs mysql?!? I don't mind it installing some useful software but Mint goes overboard. With 20.04 I'm constantly sitting at 20-27gb of used memory when doing dev work.
Earlier quoted context omitted.
Thank you - :) Reading about the cons of Snap now - "auto-updates cannot be turned off" - https://en.wikipedia.org/wiki/Snap_(package_manager)
Yep. One of many reasons they're banned in our shop. Even for client software it is bad - an app quitting out from under me because it wants to update is functionally equivalent to a crashing bug - but they're offering daemons this way, which is just insane. Who doesn't want all their containers randomly restarting because someone up the distro chain decided when your machine needed to upgrade? https://snapcraft.io/l…
This doesn't happen, at least on account of Snap. It's copy-on-write when it comes to updates, and whatever version you have running at the time of update will happily keep on running. I've been mildly confused by this a couple times, when I would end up with two different versions of VS Code running side by side, but the bright side was that my work wasn't interrupted.
It incidentally also sidesteps all the problems that stem from libraries or configuration being updated under a running application, which can happen with Apt.
Source: The Ubuntu podcast Telegram channel
Earlier quoted context omitted.
> but from the User perspective it seems like FlatPaks[1] are much better and address the issues that this article raises This is interesting, because the last few days I was actually working on packaging an application of mine as a snap/flatpak. From my PoV, they both have their fair share of issues. Snaps enforce a sandbox, which I think is actually a good idea, because the desktop security model is somewhat broken…
`curl | bash` gets a bad wrap. From a security perspective (assuming you trust web pki), it's 100% no different than a) downloading and running a script, b) downloading a package and and installing it, c) downloading a binary blob and executing it, etc. I actually find that piping an install script to an interpreter is the easiest to audit of all the options because I can see exactly the changes that will be made to…
It is bashed by those who value reproduction and discoverability:
* every person receives same script, confirmed by signature
* multiple mirrors, no single point of failure, no pull out by author (left-pad)
* no silent update (browser addons)
* tested to work on your system
* clean remove of installed files
* search in packages not in web (anti fishing)
* hosted in secure environment
* watched by many eyes
Earlier quoted context omitted.
> it is to provide an upgrade path for users of Chromium in previous Ubuntu releases to the latest Ubuntu release without breaking Chromium. Are you seriously, unironically claiming this? You broke a massive amount of native plugins. The snap auto-update mechanism fucks up Chromium's data each time because Chromium gets no warning that it suddenly can't write to the disk. Its launch time is also way worse. On top of…
> Are you seriously, unironically claiming this? Yes - because when I say "without breaking Chromium", I mean that Chromium wouldn't work at all because it wouldn't be installed following an upgrade, as opposed to some things you don't like about how the Chromium snap works but don't apply to the majority of Chromium users. Edit: you seem to be conflating your disagreement on Ubuntu's choice to move to shipping Chrom…
Because you don't ship it as a normal package any more, which is caused by you. Calling it something you did "for the users for the sake of not breaking it" is really rather nasty.
> you seem to be conflating your disagreement on Ubuntu's choice to move to shipping Chromium as a snap with a technical detail on how the upgrade path for users was achieved.
Oh I disagree with both, there's no conflation there.
Earlier quoted context omitted.
I have no nice words about the person who thought that folder is acceptable to use. Seriously, what the fuck even?
Well ~/snap is pretty terrible but I am almost as annoyed with something like ~/.tmux.conf and no support for the XDG Base Dirs Spec or setting the config path. With tmux it seems like this is finally possible with version 3.1 or by compiling it yourself but I remember being annoyed about this years ago. I dislike a home directory cluttered with dotfiles just as much as that snap folder choice because when do we actu…
Name and shame:
* docker (~/.docker)
* Arduino IDE (~/.arduino15)
* GNURadio (~/.gnuradio)
* IPython (~/.ipython)
* FreeCAD (~/.FreeCAD)
* HPlip (~/.hplip)
* IntelliJ and others (e.g. ~/RubyMine[year])
* Cargo (~/.cargo)
* Audacity (~/.audacity-data)
* PGAdmin (~/.pgadmin)
* ELinks (~/.elinks)
* NPM (~/.npm)
* sqlmap (~/.sqlmap)
* ZAP (~/.ZAP)
* GNUPG (~/.gnupg)
* crashlytics (~/.crashlytics)
* Android Studio (~/.android)
And so so so many others just crap all over home when they could just crap in .config if it's config and in .cache if it's cache. Lazy devs.
Earlier quoted context omitted.
Im here to push you towards Mint. mint is cleaner ubuntu. the wifi drivers work. the UI is really good. it just works.
Just make sure you know what you are doing. It's not one of the major distros. For the longest time you couldn't dist-upgrade it, at all. The functionality wasn't there. When their web servers got hacked, they cleaned them, and got hacked again. From a Debian user's perspective it is unclear why these small distros can't just be a Debian derivative or a Fedora spin. It's not scalable that every small distro invents t…
Like, I ain't crazy about what's happening with Mint and all of their hacks -- trust status: eradicated -- but I certainty get why they exist as a distro.