• morrowind@lemmy.ml
    link
    fedilink
    arrow-up
    87
    ·
    11 months ago

    Seems kinda inconsistent. I’m seeing thin lines, thicc lines, flat, 3d, colored and monochrome all together

    • miss_brainfart@lemmy.ml
      link
      fedilink
      arrow-up
      25
      ·
      11 months ago

      The icons don’t all speak the same language, true. Some are way more elaborate and detailed than others, which just makes them look off.

      Maybe the library could be a single book instead of an entire bookshelf, for example?

    • mbp@lemmy.sdf.org
      link
      fedilink
      English
      arrow-up
      11
      ·
      11 months ago

      Jesus, it’s so inconsistent. I suppose that may be beneficial when looking at all of your folders at a bird’s eye view but my knee jerk reaction isn’t the most positive.

  • Philip Goto@feddit.nl
    link
    fedilink
    arrow-up
    75
    ·
    edit-2
    11 months ago

    That looks… really inconsistent

    • Why is the mac icon black while the rest aren’t?
    • Why are the games/downloads icons offset while the rest aren’t?
    • Why are some icons really minimalistic and some really detailed?
    • Why do the colored folders have a line while the rest don’t?
    • Why are java/android/deb/blender colored while the rest aren’t?
    • And why is the black folder blue lol
  • SimonSaysStuff@lemmy.world
    link
    fedilink
    arrow-up
    37
    ·
    edit-2
    11 months ago

    These are definitely an improvement over the current icons but while some of the design rules are evident, i think a bit of refining is in order.

    The games and download folders both need a complete redesign as the ignore the design rules that the other folders use, and why are the symbols on each folder white except for the Mac folder?

  • Square Singer@feddit.de
    link
    fedilink
    arrow-up
    23
    ·
    edit-2
    11 months ago

    Finally designers are realizing it’s not 2013 anymore and nobody liked the Win8 designed-in-powerpoint style.

  • TurboWafflz@lemmy.world
    link
    fedilink
    arrow-up
    13
    ·
    11 months ago

    Ooh, it really reminds me of newaita reborn which is one of my favorite icon themes. I’m glad they’re making it a little less minimal

  • Resol van Lemmy@lemmy.world
    link
    fedilink
    arrow-up
    13
    ·
    11 months ago

    I’ve seen better designs. But I’ve also seen worse designs. This is pretty meh.

    And I was gonna try out KDE anyway.

  • AlijahTheMediocre@lemmy.world
    link
    fedilink
    arrow-up
    10
    ·
    edit-2
    11 months ago

    Now KDE needs to implement a consistent design language for its apps, clean up its settings, and have better defaults. Not asking KDE to copy Gnome, just that it needs a lot more work to be palletable to someone using it for the first time.

  • qaz@lemmy.world
    link
    fedilink
    arrow-up
    9
    ·
    edit-2
    11 months ago

    I actually quite like the current breeze style with the sharper edges, it sets it apart from other designs.

  • SuperSpruce@lemmy.ml
    link
    fedilink
    arrow-up
    8
    ·
    11 months ago

    I’m not the most knowledgeable on this subject, but I’m curious to learn more.

    Why do various toolkits have major releases that seem to reset the features of the last one?

    GTK 3 seems like GTK 2 but slower to me, and before the transition was even complete GTK 4 showed up, which just seems like GTK 3 but a bit different. Qt 5 works really well and is efficient on resources, so why are we switching to Qt 6? It seems like reinventing the desktop over and over again.

    I understand updates for the kernel for compatibility, small to medium updates to all software for bug fixes and new features, and major updates to toolkits when there are big problems with the current release (X vs Wayland for example). Or if the current release was unreliable and bloated, which I heard was what happened with Qt 4 and why they switched to 5. But I also heard Qt 3 was really stable and lightweight, so why did they switch away from it?

    • OsrsNeedsF2P@lemmy.ml
      link
      fedilink
      arrow-up
      9
      ·
      11 months ago

      Usually there’s big new features that accomodate more modern hardware better. As an example, Qt6 revamps support for Wayland, HDR, and scaling. Even these things on their own don’t seem like much, but if you go back to KDE 5 in 10 years time you’ll definitely feel like something is plain/dated (or completely not working if you’re on new hardware)

    • Antergo@lemmy.ml
      link
      fedilink
      arrow-up
      6
      ·
      11 months ago

      Gtk 3->4 made a lot of internal changes, and at least some were related to making wayland work. Wayland “worked” in gtk3, however it was very much an afterthought, and half the toolkit was useless under wayland. Other changes are usually required for changes related to rendering, gtk4 had vulcan rendering which may require some breaking changes. Another thing is just general breaking changes that are good, sometimes you realise some decision was bad, and a new major release is just a way to make these.

      From the end users perspective nothing much changes, it maybe looks a bit different, but not much besides that. But a vulcan renderer and being fully wayland compatible are major improvements that also improve the user experience, even if you don’t notice directly.

      • SuperSpruce@lemmy.ml
        link
        fedilink
        arrow-up
        1
        ·
        11 months ago

        Interesting. I’m guessing the changes were too big to just be added incrementally in updates to GTK 3?

        • Markaos@lemmy.one
          link
          fedilink
          arrow-up
          3
          ·
          11 months ago

          Usually the problem isn’t that the changes are big, but that the new way simply isn’t compatible with the old way to do things, and you can’t just make a change that will break existing applications in minor versions (well, there’s nothing technically stopping you, and unintentional compatibility breaking bugs have definitely happened in the past, but people are gonna get real mad at you if you do that). Even if you break that change up into thousand tiny changes over many minor versions, the end result is that at some point, you break old apps.

          The solution is to take note of all the things that are either badly designed or became obsolete and once in a while go “hey, let’s make a new major version and fix all of this crap”. With a new major version, you don’t have to worry about old applications and are free to improve your library in any way you wish, and you also get the option to keep updating the old major version with some maintenance bugfixes so that the old apps keep working well enough.