4 ms·
I thought the author addressed that point: "But this assumes that slow-to-upgrade users can have negative effects on everyone else. If one user can't have a ne
by mooreds 3y ago
I thought the author addressed that point:
"But this assumes that slow-to-upgrade users can have negative effects on everyone else. If one user can't have a negative impact on other users, then you don't care if some users are slow to upgrade; they're only hurting themselves."
There's still the support issue, I agree. If a customer paid you money and they are on version n-10, they still expect support.
> Plus, if there was anything about your service that leveraged unique algorithmic improvements or some other proprietary tech, it is now at the mercy of anyone with a decompiler and sufficient time.
This is a valid point. My answer would be: it's all tradeoffs, but if your secret sauce is so valuable that it would be worth decompiling and can't be protected with decent pricing, license terms and lawyers, run a service.
There are plenty of technologies that are not worth decompiling for your average business customers.
- LtWorf 3y agoIf your updates don't break every single time, your customers will be more likely to do them.
- jampekka 3y agoIn my experience the more they try to hide the sauce the worse it is. Quite logical though if the secret is that your secret sauce is bland and off-flavor copy of a canned soup. Which it usually is.