“When you want software as a service”
Lol. Nobody wants software as a service.
Say that to my employer who just replaced our in-house developed system with a service and made my job disappear.
And even if they did, the notion that you need proprietary software for that is a lie. There’s nothing wrong with paying a provider to host and admin some AGPL software for you.
Smaller businesses without in-house IT sometimes do, though. Sure they can get an MSP. But if their purpose is to facilitate a software vendor to connect to a server with business specific software they don’t understand, they might as well just get it as a service.
Especially when it’s software that just needs yearly updates due to changing regulations.
I definitely agree that more often than not, the above doesn’t apply, but there specific situations where SaaS actually does make sense and will have a lower cost in money and time.
Ah yes, the fabled support contracts for enterprise applications.
Where you have to answer the same questions over and over again. Don’t worry, in 3-10 business days you’ll be talking to someone who has actual experience with it. Who then labels your problem as a bug that they won’t fix soon.
Holy moly, the cookie tracker list on that site is longer than my arm! And I hate how deceptive is the “accept all” button - it implies it means "accept all settings, rather than “accept all tracking software”.
As for the article itself, the author presumes (or is being intentionally deceptive) that FLOSS is unsupported, and completely omits Canonical.
The only valid reason i agree is “don’t use FLOSS if it doesn’t support your hardware” but that probably means that you’re using highly specific hardware, or are suffering from vendor lock-in and should phase out the proprieatry hardware whenever possible.
I wouldn’t be surprised if this article was commissioned by a big tech company like Apple or Microsoft.
