If the designer of a tools explicitly says, "It's in Beta!", then it's fine as I will expect it to change, and there's a possibility of influencing that change. :D
But, if it's a full release, and the updates break the existing workflow, then why would I bother trusting it in future?
Especially when it's commercial software, as the people making those decisions are doing the exact opposite of what their job is supposed to be... :|
It also means that I am less inclined to trust that specific tool in future, as I don't know when it will change in unexpected ways.
That lack of trust is what destroys the future use of those tools.
If the designer of a tools explicitly says, "It's in Beta!", then it's fine as I will expect it to change, and there's a possibility of influencing that change. :D
But, if it's a full release, and the updates break the existing workflow, then why would I bother trusting it in future?
Especially when it's commercial software, as the people making those decisions are doing the exact opposite of what their job is supposed to be... :|
@BillySmith if it's commercial software then their job is to make money for the company — which might mean breaking your workflow, if someone thinks there is money in it. (eg: look how modern our product is, it does X like all those other ones!)
what bugs me, personally, is when FOSS software does this. Because — why the fuck?
