Yes and no. No because for things I care about a lot, and want to ensure long term support/service/updates (e.g. password manager, email host). Having a subscr

Yes and no. No because for things I care about a lot, and want to ensure long term support/service/updates (e.g. password manager, email host). Having a subscription model also means I generally know the cost of keeping up to date (no being surprised by a new $359 version to shell out for at some arbitrary point in time). Yes for three main reasons. First being that it feels like it doesn't scale with the amount of software that's trying to use that model. Sure I can easily afford a couple of $20/month subscriptions, but 20 of those? Not a chance. Second is that its a bad fit for software that I value but only very occasionally use. In such cases it feels like I'm paying way above the odds for the amount of time I use the software. Third is that I actually find it stressful to have to remember and manage subscriptions for everything. I have to spend time figuring out whether it's still worth paying, check to see if rates have changed, worry about getting locked into another year's worth of contract, etc. With a one-off app purchase it's done and takes zero mental bandwidth in future.