Re-writing and refactoring the UI would have been the optimal time to "figure out" the UX errors and shortcomings. Instead, the problems were brought forward into the new codebase where they continue to plague the software. Knowing there was a problem with the first version of the software, and the bringing that same problem forward to the next version of the software, I feel is accurately portrayed with "refused to fix".nateb wrote: ↑Fri Jan 03, 2020 10:35 amNeat. I didn't know "it's something we need to figure out" translates to "we refuse to fix it" in whatever language you speak. I'll have to keep that in mind in the future.rpcameron wrote: ↑Fri Jan 03, 2020 2:59 am
It's this attitude that keeps SD's software from being a viable alternative. They're well aware of the shortcomings of their software, they know it's been unusable, they continue to promote it, and they refuse to fix it.
Their move to a remote-hosted, React-based UI is just further proof of this user-hostile approach.
In this manner, "something we need to figure out" came out as "something we didn't care enough to address when re-writing our software", which since it was a problem before, and is a problem still, translates as "refused to fix".