I don't use Notepadqq anywhere (I use kate btw), but on my KDE Neon system it's currently showing:

$ snap info notepadqq
name:      notepadqq
summary:   A Notepad++-like editor for Linux.
publisher: Daniele Di Sarli (danieleds)
store-url: https://snapcraft.io/notepadqq
license:   GPL-3.0
description: |
  It helps developers by providing all you can expect from a general purpose text editor, such as
  syntax highlighting for more than 100 different languages, code folding, color schemes, file
  monitoring, multiple selection and much more.
  You can search text using the power of regular expressions. You can organize documents side by
  side. You can use real-time highlighting to find near identifiers in no time.
snap-id: 6iueWFAtx9P2OQz4SIW64Kry9hT8aUCL
channels:
  latest/stable:    1.4.8          2018-09-14 (855) 151MB -
  latest/candidate: ↑                                     
  latest/beta:      2.0.0-beta+git 2019-10-12 (890) 201MB classic
  latest/edge:      2.0.0-beta+git 2019-10-16 (897) 197MB classic

It seems to be a dead project (the last release on GitHub is that same 2.0 beta from 2019), but looking at the snapcraft.yaml file, it looks like it's because they're vendoring in a pretty big chunk of KDE and gtk libraries. 2019 was before I started doing anything with snaps or flatpaks for desktops so I'm not sure what the state of KDE content snaps was then (I know there was a GNOME one because the core18 gnome content snap is installed on my system for uhh... some app that I have), but these days for desktop apps there are content snaps for gnome (published by Canonical) and KDE Frameworks (published by KDE) to deduplicate those dependencies.

It was being done by a group of snapd developers at Canonical, IIRC, but after a couple of years of exactly zero interaction from anyone outside Canonical I think they just gave up and decided it wasn't worth it because they were getting accused of trying to monopolise whether they had an open store or just an open API.

Of course, you can also distribute snaps without using the snap store API. I've used this for airgapped machines in the past. You can either just grab the .snap file (which is just a squashfs file with a meta/snap.yaml in it so snapd knows how to treat it) and install it with --dangerous, or you can include an assertion file for that snap signed by a certificate that your machine's snapd trusts and not even have to do that. (Those airgapped machines trusted our own certificate so we could ensure that the snaps came from our CI process and weren't a developer's random test snap).

If you look through the desktop portals GitHub, it seems to be a mess of bikeshedding, mostly on the part of a small number of people on the flatpak side. Canonical seem to have been working around this in snaps by writing their own interfaces as stopgaps until the desktop portals catch up, probably because they got such pushback when the similar frustration on the display server side resulted in them releasing mir with its own protocol until the Wayland folks could get their act together.

Well that's what /opt is for. Well-behaved application packages that aren't part of your core distro should install themselves in there.

You don't. You spread Marmite on toast and you feed Vegemite to the bin chickens.

Ask him how he feels about all this new music the kids are listening to, like that lead Zeppelin and the beetles.

I wonder what the numbers would look like if you put in "can't afford it" as 1 year.

Apple is (rightfully IMO) far more notorious for taking something that's been around for years already, adding it to their product line (or as a feature in a product), and then pretending they invented it. Almost every company will copy features/products from other companies, but they don't usually pretend to have invented the whole thing.

Example: Gmail. It was revolutionary, but not because Google really invented much (or indeed claimed to). Rather, it was revolutionary because it provided features that already existed in paid options (e.g. full IMAP support, large mailbox sizes) for free, with a good web interface.

I don't think snaps are bad (and when someone tries to explain why they are, about 85% of the time they say something wrong enough that I suspect they're probably just parroting someone else rather than actually knowing what's going on). It's sad, because if we could get rid of the bullshit we could actually have decent discussions about the benefits and shortcomings of snaps (and how to fix those shortcomings).

On the .deb front: it's a package format made by Debian. Each archive contains a data tarball, which has the files in the package in their full structure from /, and a control tarball, which contains metadata such as name, version and dependencies as well as pre-install, pre-remove, post-install and post-remove scripts, which are used doing any setup or removal work that can't be done just by extracting or deleting the files.

The upside of deb files is that they tend to be pretty small. The downside is that this typically comes from having a tight coupling to library versions on the system, which means upgrading a library can break seemingly unrelated things. (This is why you get warnings like this page: https://wiki.debian.org/DontBreakDebian) Many third party distributors (e.g. Google with Chrome) take care of this by packaging most dependencies inside the deb, inflating the size.

Another major difference between packages like debs and rpms and newer formats like snaps and flatpaks is that the latter have confinement systems to prevent apps from having full access to your system.

I pretty consistently find the snaps to be the best trade-off of being up-to-date and stable for me. Especially for CLI tools and services.

Flatpaks and snaps both have shared dependencies, just at a less granular level than debs. OCI images and VMs are pretty much the extreme opposite of shared dependencies.

Some further context on this that @Dop@lemmy.world might want to know:

While Canonical's snap store is proprietary (which, to be clear, I don't really like), all the client software is open source and the API is well documented (though a bit janky). Their snap store relay app (which is open source) has a full implementation of it. There was a fully functional open snap store for a while, but the project died out of a lack of interest. You can also distribute snaps through another mechanism and install them locally on the machine (though you then lose the benefit of snapd's auto updates). You can even do this with snapd still checking the signatures of the snaps.

The standard for snaps is fully open, as is snapd itself.

There's no need to oversell the negatives to the point of being wrong.

The first two snaps I compared sizes of on my system are uv and bitwarden. The uv snap is 9.5 megs vs. the wheel's 12.2 megs, and the bitwarden snap is 97 megs vs. the Deb's 79 megs and the AppImage's 114 megs. These seem pretty reasonable - doubly so since snaps also have delta updates.

Wait are you actually saying Vegemite is better than Marmite?

What a weird take.

Psh, I time travelled 3 days into the future to comment on this post.

Gotta give people their Two Minutes Hate or they might remember that voting for Democrats is, for most Americans, the actual least evil option on November 5.

It's amazing how close they get to making good points before veering off into "Dems bad, do <thing that gets Republicans more power>."

This meme really doesn't fit the format. Given the standard form of the meme, you're implying that Israel are the reasonable, relatable ones here, that the warrants are unreasonable, and that someone other than the ICC has actually announced warrants.

Enunciate.

Because I didn't think it particularly important for countering this same old tired BS. But if you really want to know, it's Ann Arbor, MI and the mayor was Albert Wheeler.

(Edit and fun fact: I'm writing this from Wheeler Park right now ᕕ( ᐛ )ᕗ)

Can confirm that it can do this fairly well.

Source: the time I grabbed a machine we were about to toss and made it a secondary domain controller for our site so we could nuke and pave our misbehaving Server 2012 DC.

(That other one was also a secondary DC - we just needed one on-site so we could prevent our T1 connection to another site from being the bottleneck.)

My city had ranked choice voting implemented by Democrats in the 1970s. They elected the first black mayor, who is still one of our most beloved mayors in the city's history, under RCV.

Then Republicans made it illegal at a state level when they had a trifecta. Democrats keep introducing bills at the state level to allow RCV, and Republicans take more and more drastic action against it. So yeah... I want more Democrats in my state government so we can have RCV.

Flatpak is not a solution for packaging a large portion of the types of software Canonical packages with snap, such as database servers, kernels and containerisation software like lxd.

But if flatpak doesn't meet the widest use case of snap, are they really describing flatpak?

So why would Canonical switch to another technology that came after what they made and doesn't cover their biggest use cases for snaps?

You can download a .snap package and install it. If you add the author's signing key as trusted in your own snapd, you can even do it alongside their own assertion file.

Personally I use (and maintain) snaps for several developer tools I use, because the automatic updates through snap means I can have automatically up-to-date tools with the same package across my Ubuntu, Fedora, Arch and OpenSuSE machines.

Snaps predate flatpaks though.

Just to put that in perspective: that's less than a dollar per American for NASA and over a thousand dollars for the military.

I am a certified Linux user with over 20 years of experience.

Please run the following command in a terminal:

sudo dnf install apt

And then try the instructions above. Let me know if this fixes your issue

• certified Linux expert

We're doing really well! Only ⅓ of my city's budget goes to the cops 😬

If you're a time traveller you could build up credibility with other things too. Start contacting a journalist with predictions of future headlines. Go back to October 2000 and say what's going to happen with Bush v. Gore. Then in like July 2001 meet up with them, explain that you're a time traveller which is how you know this, and show them the video.

That's the thing - the other service is cheaper!

The way his skinsuit slides around on him I wonder if he's a very small Slitheen.

Plague Inc was one of the things that kept me sane during lockdown.

If there were an election with Jill Stein running against Ed Balls I would be handing out so many spherical foods.

It's ironic that about 50% of the phone OS stuff (that isn't actual technical discussion) I see is iPhone users complaining about Android users saying iOS sucks. 40% is iPhone users saying Android sucks, and 10% is Android users saying iOS sucks.

I'm in a place with an ecosystem that can actually be taken seriously.

Agreed. The great defaults in Plasma definitely are a major draw for me.