> For some, this might be a tough pill to swallow. But a for-profit business exists for profit. No, a business usually exists to provide some useful good or service to its customers. FedEx delivers packages. Apple makes phones and computers. Etc. > Definitionally and practically. Profit is what allows the company to hire employees, grow, and sustain itself—it is quite literally what funds ongoing development That's g…
> No, a business usually exists to provide some useful good or service to its customers. FedEx delivers packages. Apple makes phones and computers. Etc. What? If Apple or FedEx could get customers to (sustainably) pay them without actually providing a product in return, do you think they would have kept making phones and delivering packages just for the hell of it?
Open Source does not win by being cheaper
51–60 of 287 posts
Re: Open Source does not win by being cheaper
#52I've always been annoyed that companies will pay 6 figures for a support contract, but won't consider hiring a full time engineer for the same or less pay to support an open source product that does the same thing. The support contracts are often disappointing too, like you are paying $200,000+ a year for the stupid thing and they won't even fix your problems? "That product is not our current area of focus". So frust…
If a company says it is not their current focus even after paying 200k, you should looking into finding an alternative vendor who is willing to go above and beyond. A good vendor gets you by features and keeps you with exceptional service. I have seen vendors saying that those words when they are in extraction mode.
In my opinion orgs should have service contract. It is more important when you are responding to RFP and you are a b2b org. If you dont have a service contract for tools and service you use, you will run into liabilities that you don't own and can delegate it to the vendor.
Re: Open Source does not win by being cheaper
#53Earlier quoted context omitted.
Component breaks due to bug, deployment misconfiguration, scaling failure, etc., and your company loses $1M during the outage. If it's a vendor with an SLA, you can (sometimes) get them to cover the $1M. If it's in-house, you're eating it. It's often cheaper to build/run stuff yourself (unless it's so commodified that you're benefiting from amortization across the vendor's many clients), but then you have to be self-…
I don't think liability payments are that common. As someone who helps in analyzing software purchase decisions, it's certainly not something I hear people bring as a major factor.
Re: Open Source does not win by being cheaper
#54Earlier quoted context omitted.
The Caddy project is fighting to show it can work. We are having moderate success. I just gave a talk about this a couple weeks ago at an internal company event and will be doing so again at GoWest in a few weeks. The premise is that open source licenses are what they are: they grant freedom, but not other things that companies would pay money for. Proprietary licenses do offer what companies need, but at the cost of…
I love Caddy and have shilled to everyone I know, so thanks for your great work. I'm keen to hear more about your model, because I think the influx of companies abandoning their open source roots has shown the problems with the current approach. I am rooting for you folks!
Re: Open Source does not win by being cheaper
#55Earlier quoted context omitted.
- Vendor contracts are hard - So we avoid doing them - So we never get good at them - So every contract is a painful lesson in trying Open source wins because I don't have to involve the entire company to use it. I can literally just raise my voice to see if anyone in the group cares and then use it. And even when it's free for small companies, not approving a license is holding up something that we think is already…
In many companies I expect at least a security review of the open source before developers can use it. This can have a lot of red tape.
Re: Open Source does not win by being cheaper
#56Re: Open Source does not win by being cheaper
#57Earlier quoted context omitted.
- Vendor contracts are hard - So we avoid doing them - So we never get good at them - So every contract is a painful lesson in trying Open source wins because I don't have to involve the entire company to use it. I can literally just raise my voice to see if anyone in the group cares and then use it. And even when it's free for small companies, not approving a license is holding up something that we think is already…
In many companies I expect at least a security review of the open source before developers can use it. This can have a lot of red tape.
Re: Open Source does not win by being cheaper
#58> For some, this might be a tough pill to swallow. But a for-profit business exists for profit. No, a business usually exists to provide some useful good or service to its customers. FedEx delivers packages. Apple makes phones and computers. Etc. > Definitionally and practically. Profit is what allows the company to hire employees, grow, and sustain itself—it is quite literally what funds ongoing development That's g…
You would have to be grossly naive to think mission comes before profit for 99% of companies.
Re: Open Source does not win by being cheaper
#59Earlier quoted context omitted.
> No, a business usually exists to provide some useful good or service to its customers. FedEx delivers packages. Apple makes phones and computers. Etc. What? If Apple or FedEx could get customers to (sustainably) pay them without actually providing a product in return, do you think they would have kept making phones and delivering packages just for the hell of it?
Hah, "if" - as if every company isn't actively pursuing recurring revenue models right now.
Re: Open Source does not win by being cheaper
#60I've always been annoyed that companies will pay 6 figures for a support contract, but won't consider hiring a full time engineer for the same or less pay to support an open source product that does the same thing. The support contracts are often disappointing too, like you are paying $200,000+ a year for the stupid thing and they won't even fix your problems? "That product is not our current area of focus". So frust…
If you hire an engineer, the liability is your problem. If you donate to open source, liability is still your problem. Both of these situations are patently unpalatable for most businesses. Meanwhile, if you pay someone for a support contract the liability is their problem. You see, whether a problem that comes up is fixed is actually irrelevant. The real question is how much liability you can get rid of.