• nehal3m@sh.itjust.works
    link
    fedilink
    arrow-up
    27
    arrow-down
    5
    ·
    2 days ago

    Eh. One thing proprietary software has going for it is clear design goals and the leadership to create a cohesive UX. Open source projects tend to be a grab bag of tools that work well for developers.

    Not saying I don’t love FOSS, but there’s definitely stuff that proprietary software does better in a practical sense, whatever else your opinion of it.

      • MMNT@lemmy.world
        link
        fedilink
        arrow-up
        11
        arrow-down
        1
        ·
        2 days ago

        I am a designer with 20 years of experience. I’ve tried contributing to FOSS, but the developers are incredibly stubborn and work purely guided by their own assumptions. Hence the horrible UX on so much FOSS. There are more than enough design people that would love to contribute, but are met with nothing but ridicule and insults.

        • index@sh.itjust.works
          link
          fedilink
          arrow-up
          2
          arrow-down
          1
          ·
          2 days ago

          That has not much do to with FOSS but with the people you are working with. Proprietary software you can’t even contribute freely to begin with

    • yonder@sh.itjust.works
      link
      fedilink
      arrow-up
      3
      ·
      2 days ago

      As someone who uses Gnome familly applications daily, I have to disagree with the notion that bad UX is fundamental to FOSS software. The gnome apps and shell all follow the same set of UX guidelines and feel quite cohesive as a result. I can definetly see where you get the idea of bad UX in foss though (looking at you, GIMP and Libreoffice)

      • nehal3m@sh.itjust.works
        link
        fedilink
        arrow-up
        2
        ·
        2 days ago

        I’m not saying it’s fundamental, sorry, I should have specified. You’re exactly right, GNOME is driven by it’s Foundation and so there is leadership in place to make sure that the software ends up as a cohesive whole. Software projects that don’t, or that create one after the fact, tend to be a lot less so.