Jegahan

joined 9 months ago
[–] Jegahan@lemmy.ml 4 points 6 months ago* (last edited 6 months ago)

Unlike Gnome, KDE do actually care about their users, not just about themselves.

It's hilarious how, despite KDE apps being broken on every DE that isn't plasma, people will still find a way to blame Gnome for it.

Contrarily to KDE, Gnome has managed to make sure that libadwaita apps look and work just like they're supposed to and how its shown on the screenshot in the app store. You might not like the theme, but at least you knew what to expect before downloading, whatever distro you are on.

It's great that KDE finally managed to fix their app so that they come with everything it need to function properly. People might be able to use them now on other DEs.

[–] Jegahan@lemmy.ml 3 points 7 months ago (1 children)

If I remember correctly they do have rollback, at least in openSUSE Aeon (the immutable version based on Tumbleweed) . It just using btrfs snapshots

[–] Jegahan@lemmy.ml 3 points 8 months ago* (last edited 8 months ago)

Man this Missinformationen is hard to squash. Yes Flatpaks absolutely share libraries. These are called runtimes and are shared between all the Flatpak apps that use the same version of it. You will only get more than one version of a given runtime if some apps need this other version. For most runtimes that I know of, most only have 2 currently maintained versions, so I almost never get more than that on my system (and when I do, app devs tend to update their apps shortly after so that they're using a maintained runtime). For example on my system where I mostly use GTK apps, I only have two versions of the Gnome runtime (44 and 45). And even when you have more than one version of a runtime, they get deduplicated, so even runtimes share parts between them.

If you're interested here is an article about it.

[–] Jegahan@lemmy.ml 5 points 8 months ago* (last edited 8 months ago) (1 children)

By the way, if you guys are interested here is a talk comparing Appimages Snaps and Flatpaks by Richard Brown, one the devs at Suse, a big contributer to openSuse and the guy who spearheaded the Desktop variante of MicroOS (the immutable openSuse Tumbleweed).

He isn't to keen on appimages either because of a miriad of technical issues.

[–] Jegahan@lemmy.ml 4 points 8 months ago (1 children)

And they explained why this opinion is kind of silly.

"I will not listen to anything this person has to say, because I don't like a small and inconsequential part of their presentation" is not a great opinion to begin with, even ignoring the fact that this presentation might be necessary to reach a meaningful audience.

[–] Jegahan@lemmy.ml 11 points 8 months ago

To be honest, this seems to me like a pretty bad take with weird and kind of BS arguments. Why are professional designer, both those working for some of the biggest tech companies and those working in open source project, making these choices? It couldn't be for actual reasons or because they actually prefer it like that. No, they are "afraid of color". Or implying that dark theme exist because of these black on white themes, as a mean to escape it. It just weird backwards logic to justify his taste and shouldn't be necessary to just state that he prefer a different kind of themes.

To me, the Windows themes he showed as positive examples look way to cluttered and busy, even though they don't show this much information. I don't need the theme to be "exiting", I need them to display the information in an easily readable way. And dark theme aren't there just for people who dislike the modern light theme. Having a light and a dark theme (and ideally having the app follow your system preference) actually serves a purpose. You can actively switch between them depending on the context, the time of day, the brightness of the room or any other reason to make the screen easily readable and comfortable to look at.