• 2 Posts
  • 50 Comments
Joined 1 year ago
cake
Cake day: July 28th, 2023

help-circle












  • If you remove the app-platform role from Nextcloud by separately hosting the individual apps, what benefit do you get from having both Nextcloud and File Browser?

    Nothing really. For almost any Nextcloud feature out there, you can find a server app that does the same.

    But that’s the point in my opinion. I don’t want to waste time managing tons of apps if I can manage one Nextcloud instance. Nextcloud basically decides for me what’s the best way to get those features running, so I don’t need to figure out myself.

    Now if you’re into self hosting one container for each feature, go for it, no reason to not do so.






  • This hate comes mostly from Linux communities like here and on Reddit. When you see actual numbers, both are widely used for production use. They have lots of active users as reported in their respective blogs and websites.

    That said, it is aware that both had problems. Most hate towards Flatpaks that I can see is from purists that prefer their distro shipping their packages with dynamic dependencies and uprated by their package manager. Also there is complains with outdated runtimes and stuff like how sandboxing works.

    Snaps has all problems than before with some extras. When they were released, because of compression, they were painfully slowly to open and they affected boot time. Nowadays this is mostly gone, but they still keep a proprietary store, inability to have multiple repositories (stores) and they don’t respect your home directory structure by placing a “snap” folder in your home.

    Personally I use both and I’m happy with them. The proprietary store stuff does not bother me because I’m already trusting canonical binaries by using Ubuntu and they are easy to use and be productive with them.




  • As an addition to other responses, think that most apps (specially smaller ones) are developed using some framework or set of libraries that might or might not support those protocols.

    So let’s pretend that I have an app buit using Electron and that framework does not support Wayland. There’s nothing I can do on the app side until Electron supports Wayland in this fake example.

    So it actually takes time for the libraries to support the new protocol and then app developers to update their apps to support it aswell.

    That’s why you see that the Wayland migration is incremental and not all at once.