Find all the best dev content at https://daily.dev/fireshipRemember, for every paid SaaS, there is a free open-source self-hosted alternative. Let's take a l...
  • thesmokingman@programming.dev
    0·
    4 months ago

    It’s very misleading to say “paying for software is stupid” and not consider the total cost of ownership. TCO includes things like infrastructure and maintenance. As an exec, I am constantly faced with two choices: free software that might do what I want or paid software that sort of does what I want. At face value, you would immediately tell me to get the free stuff. That’s where you miss TCO.

    (Read the last paragraph if you think the business lens is bullshit)

    Every FOSS solution I run requires me to deploy and maintain it. I only have so many hours in the day so at some threshold I have to hire more and more people to deploy and maintain. Integrating? That’s on me too because I’m using free software so now I need a resource to glue things together. My “free” option actually costs a portion of my engineering resources. I’m also on the hook for failures. Running my own ERP? I need to have support staff on-call to handle outages.

    Every paid solution I run costs can require some of those things. Let’s ignore paid licenses and just focus on things I can completely outsource. This means I’m no longer on the hook for deployment and maintenance, so if I can show the cost of the paid software is less than my TCO, it’s a better deal. If I have a good relationship with the vendor, I might be able to delegate my integration needs to their product pipeline. I might be able to purchase a support contract that’s cheaper than running my own.

    At some point every company will outgrow certain software. It’s a constant reevaluation of the costs of paid vs TCO of free and when I need to spend resources making it do something it doesn’t. A managed telemetry stack like Sumo or New Relic allows me to scale quickly but cheaply until I have the revenue to build an in-house team to instrument fucking everything.

    The exact same logic applies to my time. I could run free everything. That comes with a higher TCO (usually). I say this as someone who has rebuilt dot files repos on the dot every three years and been running Linux since you could get it in a book at B Dalton at the indoor shopping mall so my tolerance for personal TCO is very high. However, I don’t change my own oil. It’s free! I could do it myself! I don’t want to. I buy certain things, like software, in my personal life because the TCO of FOSS is higher than I want to pay. I have outgrown Windows and Mac so I have some level required cost in Linux. I pay for some things like storage and routing solutions even though I could build and deploy and maintain all of that myself. Sometimes I just want my shit to work and not have to do it myself.

    • nickwitha_k (he/him)@lemmy.sdf.org
      0·
      4 months ago

      This is a great perspective to voice. Sometimes those of us who are staunch FOSS advocates can lose sight of the big picture. If one’s goal is to be, for example, an eCommerce software vendor, it probably doesn’t make sense to build and maintain your own DB stack or Internet infrastructure even though it is technically feasible. The money and resources needed to maintain that stuff will take away from the ability to improve and maintain the eConmerce application.

    • howrar@lemmy.ca
      0·
      4 months ago

      An important component of the cost to consider is how long we expect a company to support a piece of software, and how much it would cost to migrate everything when they drop support. FOSS wins in this regard, especially if you can get a support contact with the devs.

      • thesmokingman@programming.dev
        0·
        4 months ago

        Neither wins here. I cannot tell you how many libraries I have had to replace because FOSS devs move on. It’s probably greater than the number of products I’ve had to abandon for lack of support but I’m not sure what that is at a percentage level. In the DevOps world everything burns constantly, paid and free.

        • howrar@lemmy.ca
          0·
          4 months ago

          It wins in the sense that you still have access to the software and code, and you have the option to either hire someone new to maintain it or switch to something else. Closed source proprietary software only leaves you with the latter choice.