Free is never free
-
@breffni-potter said in Free is never free:
- Cost of training, do you know how to use it?
- Cost of deployment
- Cost of migrating from 1 system to another
- Cost of reliability, is this tool reliable? Is it tested? Is it safe?
You realize that paid software suffers that entire list as well, right?
-
@dashrender said in Free is never free:
@breffni-potter said in Free is never free:
- Cost of training, do you know how to use it?
- Cost of deployment
- Cost of migrating from 1 system to another
- Cost of reliability, is this tool reliable? Is it tested? Is it safe?
You realize that paid software suffers that entire list as well, right?
And has a lot of risk as well, like all of these licensing risks and more.
-
@dustinb3403 said in Free is never free:
@dashrender said in Free is never free:
@breffni-potter said in Free is never free:
- Cost of training, do you know how to use it?
- Cost of deployment
- Cost of migrating from 1 system to another
- Cost of reliability, is this tool reliable? Is it tested? Is it safe?
You realize that paid software suffers that entire list as well, right?
And has a lot of risk as well, like all of these licensing risks and more.
Paid software has every risk that free/open source software has, PLUS all the other things.
-
@breffni-potter said in Free is never free:
Now let's look at free software. Starts with the words "I want a free thing which solves this specific problem" It could be CRM, Finance, Security, It does not matter, the problem is we often look at open source software as being fantastic because it is free.
That's weird. I normally look at it as superior because it has better licensing that protects me and often takes less work to maintain. Open source doesn't carry the cost (risk) of proprietary licensing and doesn't have any limits on deployment scenarios. In comparison, it's not free, it pays you
-
@breffni-potter said in Free is never free:
- Cost of training, do you know how to use it?
- Cost of deployment
- Cost of migrating from 1 system to another
- Cost of reliability, is this tool reliable? Is it tested? Is it safe?
Who pays for all the above? Have you factored it in?
Who pays for this with proprietary software? On proprietary software this is normally even more. The real question isn't if we are factoring this in to open source, it is whether you are factoring it in to closed source!
-
The thing about free software is that you can't sell it as free software to management. The way you should sell it is - The software has no license fee, and the license allows us to basically do what we want, but in every other respect, it's like normal software.
This is probably mostly a failing of IT to present the solution correctly to management. Instead they go forward with the blinders on and simply tell management - hey this software is free, and we should use it. But as mentioned by the OP, the only part that is free is the license to use the software, every other aspect is pretty much normal (testing, deploying, training, updating, etc).
-
@breffni-potter said in Free is never free:
IT professionals can introduce you to lower cost, lower risk, faster and more reliable tools to get stuff done but none of it is free. If anyone ever says "free tool" someone is paying for it.
This is something that people say, but it is an unfounded "thing people say." Like "you only get what you pay for", or "the best things in life are free" or "don't put all your eggs in one basket." It's just a saying, it doesn't have any basis in reality.
Yes, someone has to pay for everything. But some things are already paid for and the cost doesn't change whether you use them or not.
-
@dashrender said in Free is never free:
The thing about free software is that you can't sell it as free software to management. The way you should sell it is - The software has no license fee, and the license allows us to basically do what we want, but in every other respect, it's like normal software.
Right, you should be selling it the same as closed source - based on the merits of the software, the TCO and ROI, the risk reduction from licensing protection and so forth.
-
-
@scottalanmiller said in Free is never free:
From a few days ago....
Specifically about why this exact myth persists!
That's a really bad screengrab... Reminds me of
Back to the topic at hand.
-
@breffni-potter said in Free is never free:
If you are offered free, be suspicious, if someone offers you something at a big discount, beware.
Sure, but don't be any more wary than if you are asked to pay for it. Beware in both cases, but open source gives you far less reason to be worried, because it provides more protections for you out of the gate. That doesn't mean you get to go in with your eyes closed, but you are starting from a safer position.
-
@breffni-potter said in Free is never free:
Sometimes you do get a generous gift, sometimes you really do get a good deal but most of the time, its a trap for later down the line.
Except in open source software, where I've never even heard of a rumour of this existing. Could it? Maybe. But how? Thanks to the miracle of the open source license, you are protected from this quite significantly. Can you come up with any example where your fear has come true?
Linux, LIbreOffice, MySQL, PostgreSQL, Hadoop, FreeBSD, OpenBSD, Firefox, Rocket, Zimbra, Postfix, Sendmail, Apache, Nginx, Atom and so on and so on are all examples of the total opposite. I've never had anyone present or experience something like you describe as a fear to be wary of.
-
The real thing is that free is normally better than free... not only does it not cost money, it generally makes you money long term in comparison to non-free options because it tends to lower the cost of licensing, management, documentation and so forth. So it is negative cost, rather than positive.
Far more important is being wary of people selling software. Free software isn't sold, so there is rarely a person out there "selling it" to you. But non-free software is normally pushed by salespeople that make money by trying to make paid for software sound plausible. And often it is, but there are lots and lots of people on there paid to push things that cost you a lot of money. That's the biggest concern in this space.
-
Even MSPs and consultancies have a strong incentive to push closed source, even if they are not the ones selling licenses. Windows and Linux are a perfect example, or MS Office and LibreOffice, or MS SQL Server and PostgreSQL. In all of these cases, not only is there no money to be made "selling" the free option, but the profits from managing them are minimal. Companies that support all of these can tell you that a customer buying MS products is going to easily pay 200% - 400% more in support costs on average.
Whether because the software is just slower to set up, breaks more often, encourages the customer to screw it up themselves, requires more resources, has customers spending more time looking over shoulders, requires loads of licensing management time, can't use simple deployment methods or whatever - there is big, big money to be made in steering customers away from a lot of open source packages. There just isn't enough support hours generated by the simpler, more straightforward software so close source is often promoted. Everyone does it, so it's unlikely that customers will notice the bias based on increasing their support bill, especially as the bills come over time rather than all at once and carry on between vendors.
-
Hehe
-
That's a lot of interesting points on both sides. Question though, would it be better, as a consultant, to just use open source for clients and make money by supporting it slowly and over a longer period of time than many MSP'S do with proprietary software? I am thinking yes to this myself because from a clients point of view your solution worked better with far less support and they will then be happier and more likely to recommend you to others to get you more work. I believe this extra work would more than make up for lower support fees by using proprietary software that doesn't work as good. Am I completley off base or not?
-
@jmoore said in Free is never free:
That's a lot of interesting points on both sides. Question though, would it be better, as a consultant, to just use open source for clients and make money by supporting it slowly and over a longer period of time than many MSP'S do with proprietary software?
No, for two reason:
- Licensing is never the driving factor is "what is good". Open source licensing is always better than closed source licensing. Always, no exceptions. But licensing quality, while important, is nowhere near the most important thing in deciding on software.
- As a consultant, open source is not your friend. You make your big money supporting closed source software because it is almost always harder to manage, requires more support hours, and you have whole extra categories of things to manage. It's not very ethical to recommend closed source because of this, but it is why closed source is so popular even with the people who don't have to pay for it. Everyone wins from closed source in general - except for the final customer.
-
@jmoore said in Free is never free:
That's a lot of interesting points on both sides. Question though, would it be better, as a consultant, to just use open source for clients and make money by supporting it slowly and over a longer period of time than many MSP'S do with proprietary software? I am thinking yes to this myself because from a clients point of view your solution worked better with far less support and they will then be happier and more likely to recommend you to others to get you more work. I believe this extra work would more than make up for lower support fees by using proprietary software that doesn't work as good. Am I completley off base or not?
That's the rub isn't it. Finding new work to fill the time that not supporting those free things leave you with.
-
@jmoore said in Free is never free:
I am thinking yes to this myself because from a clients point of view your solution worked better with far less support and they will then be happier and more likely to recommend you to others to get you more work.
Sadly, especially in the SMB, this is not how customers think. Open source systems often have too little visibility and the customers don't understand everything that is happening. You'll actually far more often get more recommendations by overbilling and providing bad, but highly visible, support. Systems that "just work" are rarely what make customers "feel" happy. This is one of the saddest points of IT work - doing the best thing for your customer rarely is beneficial to you or is even appreciated by the customer. Often they will drop you just because you did too good of a job
-
@jmoore said in Free is never free:
I believe this extra work would more than make up for lower support fees by using proprietary software that doesn't work as good. Am I completley off base or not?
If you are dealing with enterprise customers concerned with actual profits and that operate on math and logic, you are totally correct. Finding customers that appreciate this in the SMB is very, very hard.
