|
|
|
|
|
by jcrawfordor
2302 days ago
|
|
There were still internal costs related to running IRC though, assuming you weren't paying some provider to do it for you... not large internal costs, but I don't think on a radically different scale from Slack considering that you could also view a Slack subscription as covering a client with a lot more features than a typical IRC setup (sure you could run a web client, bouncers, services, but that's all increasing your internal costs). I guess my point is that I feel like what GP refers to as "free" is actually just "developed/operated/maintained internally"... these commercial services are still by and large based on free software but you're paying someone else to do the work your internal IT capability used to do. This couples with a general trend I've observed of organizations shifting their IT workload from inside to outside via PaaS/SaaS providers. This could be viewed as a form of outsourcing... in the '90s enterprises were moving their IT functions to India. Now they're moving them to a hundred different contractors, each supporting one system. |
|
Bonus, unlike SaaS, you have complete control over the damned thing. New "features" won't suddenly get added to your tools that break your workflow, you can add new features if you need them without begging some vendor to whom you are a tiny insignificant nobody, etc.