CorvusRuber The idea I think is Solus will always default to software from repository even if it's available as both flatpak or snap.
brent Well, you can call terminal application from GUI. Many GUI application is actually a wrapper to its CLI application.
Plug in based refer to how Solus will list the packages to install. So each package management system will represent as a plugin in the new Software Center. It will makes everything easier if later down the line we have some new "Universal" package manager (maybe snappak! /s), we only need the plugin for the new one.
brent Offtopic but "sol daemon will also have a Third Party backend to facilitate installation of Third Party repo items using ypkg, which would not otherwise be supported by Flatpak or Snaps (such as Google Chrome)."
Some application isn't packaged as Snap or Flatpak, so Solus still need to facilitate the user of that packages. It refers to that.
I'm going to say this, the user actually shouldn't really concern them self with how the package manager works its magic. The end result for the user shouldn't really change between different package manager (and the transition should be painless). The biggest different actually will come for people that use CLI package manager and it's only the syntax, eopkg to sol. But how they works, the casual user doesn't really need to know.
