3 ms·
I'd point out that "software subscriptions" and "software keeps working even if you don't pay" can both be in place. For something like this, it's not a half-b
by jerf 11y ago
I'd point out that "software subscriptions" and "software keeps working even if you don't pay" can both be in place.
For something like this, it's not a half-bad business relationship; the incentives are well aligned for everybody.
For something as fundamental as build software, I'd be nervous about committing to anything where whether I can use the software I already have in two years is in somebody else's hands. I really want to be able to squirrel away complete build environments and know I can build the thing I sold two years ago again if I have to release a "my business may die if I don't" update. Remember, in two years, the "somebody else" may not exist to give me permission. Then what?
The incentives here aren't so good if access to the software is actively being removed for non-payment... the vendor is extracting small values from their customers by forcing their customers to take hidden, but actually quite staggeringly enormous, business risks.