Hot take: adobe products also have shit UI and are actively being made worse; it’s just that people are used to it (at least until adobe decides to change something again)
At least UIs are standard now, back in my day (and still some today) people would make everything a CLI and then bitch at you when you told them that their very computationally efficient video trimming tool is cool and all, but editing video from the terminal is worse than CBT.
Yeah, there are lots of FOSS projects that have very obviously never had input from an artist or UI designer. The Venn diagram of “people who have the programming skills to make good FOSS” and “people who know how to design a good UI” consists of two almost entirely separate circles.
There’s also the attitude that you’re seeing in this thread, where if people had a problem with UX the response from the devs is basically “skill issue, git gud”
Most people don’t have the skills to improve UX themselves and it shouldn’t be a requirement of any software aiming for mass adoption. Frankly if you have users familiar with the product space reaching for a manual you’ve failed at UI design. It is entirely possible to design a new UX that people can still pick up and use largely without assistance
To be fair, open source apps usually have terrible UI
Hot take: adobe products also have shit UI and are actively being made worse; it’s just that people are used to it (at least until adobe decides to change something again)
I’m not thinking of any Adobe competitors, actually.
At least UIs are standard now, back in my day (and still some today) people would make everything a CLI and then bitch at you when you told them that their very computationally efficient video trimming tool is cool and all, but editing video from the terminal is worse than CBT.
What do you mean? There is nothing wrong with a CLI tool.
Okay, I can get behind that.
Yeah, there are lots of FOSS projects that have very obviously never had input from an artist or UI designer. The Venn diagram of “people who have the programming skills to make good FOSS” and “people who know how to design a good UI” consists of two almost entirely separate circles.
There’s also the attitude that you’re seeing in this thread, where if people had a problem with UX the response from the devs is basically “skill issue, git gud”
If it’s documented… Skill issue or help out.
Good UX greatly reduces the need for documentation.
Most people don’t have the skills to improve UX themselves and it shouldn’t be a requirement of any software aiming for mass adoption. Frankly if you have users familiar with the product space reaching for a manual you’ve failed at UI design. It is entirely possible to design a new UX that people can still pick up and use largely without assistance
And let’s not forget that FOSS is unfortunatly often just awful Elektron apps
Mainly the good ones. The ones with the super polished UIs are most of the time aislop