3 ms·

I personally hate rose-colored visions of the past, of which this is one that I commonly run into :) Other things I hated: 1. yearly support contracts that we

I personally hate rose-colored visions of the past, of which this is one that I commonly run into :) Other things I hated: 1. yearly support contracts that were basically a necessity to purchase alongside (very expensive) enterprise software. 2. working at companies that had ancient versions of software running, and needing to dig up old matching documentation (when possible) 3. paying a large sum for a piece of software and then being "stuck" with it due to the investment being already made 4. the opaque sales processes that surrounded getting up & running with any piece of software

annoyingnoob 7y ago
There are plenty of software packages with perpetual licensing that do not operate Oracle-style licensing BS and support. My experience with SaaS support is terrible. In my recent experience, software with Oracle-style licensing BS offer way better support. The flip is of being 'stuck' on a version is constant updates. Oh, they decided that the UI need a complete revamp over the weekend and now everything runs slower as folks learn the new interface that was foisted upon them. Or a SaaS decides to change its API and our custom integrations break. Not all SaaS platforms are good at communicating change and preparing users for change. Sending an email to the accounting person that paid the bill about the API change does no one any good. It seems we could argue this in either direction. Point is that some things I would like to buy perpetual, for reasons, are only available as SaaS. For the most part, in my case, SaaS isn't the best answer but in some cases I'm stuck with it. SaaS drives up costs, and frustration levels among the staff.