It's no surprise that most open source software is clunky and hard to use whereas closed products always have that visual polish.
It's no surprise that most open source software is clunky and hard to use whereas closed products always have that visual polish.
And often big projects have, similar to closed source software, rather ugly workflows where you have to discuss stuff before you're assigned to a bug and then have to send it patches and what not.
A good review process is important or else everything ends in chaos.
Closed products always have that visual polish
Wow. You must use different closed-source software to me. I agree a lot of open source software is very ad-hoc and seems to have no overarching design in place, but the same seems to be true of most closed source software in my experience.A lot of open/free projects are indeed "hobby" projects (and not in a good way) -- but to claim that all of them are bad? Compared to what? The shareware scene from the 90s?
Creating a Pull Request doesn't mean that the developer of the open source project has to accept it verbatim if it doesn't fit with the 'vision.'
[Also, I'm pretty sure that the parent to your post was talking about bugs that probably don't involve visuals.]