|
|
|
|
|
by smashed
1335 days ago
|
|
My first encounter with snaps was launching gcalc, the basic built-in calculator app. At some point after an update, launching that app would take multiple seconds. How could the most basic gtk app be so slow to launch. Investigating further, I found the update had transformed the normal gcalc package into a snap, probably just to prove how great snaps could be for desktop apps? What a bad way to introduce your latest tech canonical. From then on, my opinion of snaps was very negative and I still do everything possible to avoid them. Even if they are technically great or more secure, canonical messed up their introduction and are now stuck pushing a dead horse. |
|
My first brush with fat-packages was Digikam stopping producing .deb packages, it put in so much overhead I couldn't run it on my (admittedly weak) system. The forced use of Firefox snap lost configuration, then failed to work properly (permission problems) ... it's like how the use of file managers via sudo was stopped, seemingly without a proper plan to replace it; make the new tech first, then implement it when it works! It's like going back to Windows, having fragmented app sources and forced updates that wreck everything.
I'm not sure where to move to next, I came to Ubuntu years ago because I no longer wanted to do the config work necessary to run Slackware. Looks like Mint/Arch/Debian are contenders.