• @Caronte
    link
    54 years ago

    The proposal looks a lot like what KDE is to me. Some ideas I agree with, like the use of applications that work together in a UNIX way, but I don’t agree with the point that the UX/UI trends of 2010s have regressed the usability of the desktop. Flat design makes things a lot more recognizable and provides a clean workspace and workflow. Also, there is a thing that’s too many customizability. Users can feel burned by the amount of things you can customize, and the vast majority of them don’t even change their desktops from the default settings.

  • @clockwise_bit
    link
    34 years ago

    I think the author has a great point and it’s shameful that only a handful of applications respect that philosophy.
    The best example I can think of a program that for the most part follows the described approach is mpd (maybe even mopidy, haven’t used it yet though). It integrates so easily in applications, desktop environments, less known status bars, terminal interfaces… yet it’s not tightly-coupled, it just exposes and endpoint for commands.

    While separating interface and application adds more work to the list of tasks an average joe has to accomplish, it has been proven to help a lot with the separation of concerns that in turns translates to tidier code and thus potentially less bugs in the program.

    It’s true that it makes the programs a bit less efficient, but with the amount of raw calculation power we can harvest even from the smallest of computers, I’m honestly confused as to why we keep writing coupled UIs.

    (Then of course there are exceptions, like games and other programs)

  • @jaex5Fox
    link
    2
    edit-2
    4 years ago

    deleted by creator