6 ms·
I stopped trying to debate open vs. closed software in a business setting long ago. There is a time and place for both, and rational actors will evaluate the tr
by PragmaticPulp 6y ago
I stopped trying to debate open vs. closed software in a business setting long ago. There is a time and place for both, and rational actors will evaluate the tradeoffs given their circumstances.
When people start believing that open source software is inherently superior in every situation, or that ideological purity is the most important consideration, they aren't making decisions in the best interest of the company. Engineers are especially prone to overestimating the downside risks of using closed source software (A long list of what-ifs such as "What if the vendor goes out of business without warning?") and underestimating the downsides of using open source alternatives (Notably, the inability to pick up the phone and have another company's engineers deal with the problem, per your contract). The situation is compounded by engineers who genuinely enjoy tinkering with open source software on the company's dime and, frankly, would prefer to be paid to do so rather than purchase a more efficient closed-source solution.
Of course, there are some situations where open-source software is practically superior to alternatives. I don't claim to suggest otherwise. However, the endless debates about ideological purity and avoiding hypothetical edge cases with 3rd party vendors frequently cloud decision making abilities in a business context.
For personal and open source projects, I'm all-in on free software alternatives. For business purposes, I'll evaluate the available options and try to make the best business decision for the company.
- aplummer 6y agoThis is why I like the open source + enterprise contract if you like model so much.
- alexilliamson 6y agoWhat's your favorite such example?
- deleted 6y ago[deleted]
- Arnt 6y agoI know at least four quite different examples. But they share one trait: They're quiet, softspoken, avoid controversy on internet forums. I won't name any of them. One uses low pricing, is likable, and provides a fine list of enterprise features. The HN crowd will realise that these features are really different ways of describing a very small amount of code. But if you want to spend your employer's money and don't care to spoil that by telling your managers too much, the list is fine. Engineers who like the likable make money be spent. One writes per-customer code on top of largely the same body of code, and charges very high prices, largely because they clearly know how to get stuff done using that code. They have the references to prove it, and they wrote the code, and the customers accept that they invoice customers for improvements to the free base too. One uses a technique I don't understand at all. It's different from the other three, and it works. I mention it to say that the other three aren't an exhaustive list. The fourth targets nontechnical customers and sell SaaS, I don't know the price level. You can git-clone the code and selfhost if you want, they'll be friendly but not helpful. If you make a PR on github they'll at least look at it.
- DoctorNick 6y ago...why wouldn't you name any of them?
- whatshisface 6y agoThe first one sounds like the commenter knows that their boss would cancel the contract if they realized what was going on, so the parent is taking careful steps to avoid talking about what they don't want their boss to discover.
- rriepe 6y agoIt's called the chilling effect. The most 'chilling' thing about it is that it's entirely rational.
- Arnt 6y agoBecause there are quite a few quarrelsome, overly opinionated, arrogant people on HN.
- ineedasername 6y agoWould RHEL fall into that category?
- Privacy846 6y agoThe logical endpoint (regarding purity) of free software is communism, so you’re right that it doesn’t make sense to pursue it 100% in the context of for-profit (presumably) companies.
- dnautics 6y agoDepends on the model. Probably the less restrictive models lean towards proudhon/tucker style anarchism more than marxism.
- deleted 6y ago[deleted]
- deleted 6y ago[deleted]
- zapzupnz 6y agoEven when the means of production are in the hands of the workers, that presumably doesn't necessarily equate to accepting the workers tinkering all day, getting nothing done.
- Privacy846 6y agoI don’t know what this means.
- sudosysgen 6y agoWhat they are saying is that in a hypothetical communist/socialist society, even if the entirety of production is organized by workers, it doesn't mean that they aren't going to be productive in actually building stuff, nor that they aren't going to get stuff done. How that relates to your argument I don't exactly know, but I guess it could be interpreted as saying that even if you admit that philosophy doesn't mean that you can't produce ""profit"" - especially if it is limited to software. Also, in theory, you could be 100% accept communist philosophy yet operate a for profit business.
- yellowapple 6y agoI think you're downplaying the risks of non-free (or at least non-transparent) software in an enterprise setting, and overplaying the "value" of the vendor being able to provide meaningful assistance. Speaking from experience: even if a software product is not freely licensed, there is immense value in source code being available and - better yet - modifiable (whether directly or through plugins) when trying to troubleshoot issues with that software or integrate it with other software or adapt it for your business' needs. Further, if your company's finance department is worth its salt, any such customizations and integrations are assets with real value, so even if your company's engineers are "wasting time" tinkering, the company can - and should - still capture this value on the books. And further speaking from experience: with relatively few exceptions, I've found enterprise software vendors to be pretty much useless in terms of support, and to be more often than not an obstacle to business operations than a value to it when things go wrong. All for a pricetag that doesn't even come close to justifying their meager SLAs (that they'll inevitably weasel their way out of anyway). The decision to use transparent software is more often than not a decision in the best interests of a company. Transparency is a dependency of trust; without that transparency, you have no real way of knowing whether you can trust your business on it.
- hertzrat 6y agoAnother huge benefit is that the foss software won’t just disappear if the company has a bad quarter. If the maintainers or developers leave the project, in a pinch you can make a bug fix yourself or at least legally preserve a copy of it. It’s a major risk that an offering you depend on might change or disappear if it isn’t foss
- aidenn0 6y agoMany companies will agree to escrow their code (at the customer's expense) against the risk of them going out of business. I've never actually seen it happen, but it definitely has been offered when that concern was raised, and once the customer has to pay for it, they immediately say not to bother.
- 6y ago
- kelnos 6y agoI think you're still missing the point: the freedom bits are not there for "idealogical purity", they're there because they provide practical benefits: the ability to inspect and modify the program's source code, and to build and run modified versions, without getting anyone's permission to do so. The FSF does believe that there ethical components as well, but you need not subscribe to them to see the benefits of free software. I think you overestimate how helpful a paid support option is. I've spent time working with the vendor of closed source software to get issues resolved; it's often incredibly painful and time consuming, and meanwhile the business is not able to realize the full benefit of the software they've paid for. Meanwhile, I have never run into an issue in open source software that I wasn't able to fix on my own (absent help/response from upstream) or at least figure out a workaround, often one that would not be possible to figure out without source access. (Note that I'm explicitly ignoring the kind of "fit for purpose" issues that you're never going to resolve, period, whether it's closed or open.) Adopting open source is not without its own risks, but it does give you many more options than any closed alternative ever will. If your business does not value that difference, then that's fine, as long as you've made that decision with open eyes.
- dividedbyzero 6y agoAs a poor old 1x dev, I absolutely cannot fix any arbitrary complex issue in any arbitrarily large codebase written in any language at all, using any obscure build tooling, any complex framework, any architecture pattern at all, while not breaking anything else, within a timeframe that doesn't make most commercial support response times look enticing.
- ohazi 6y agoMaybe not, but you can probably write a python script to parse the (open, documented, text-based) file format of an open-source tool and perform some important action that the tool doesn't support. Or maybe someone already wrote a library that parses the file format which lets you jump straight to pulling out the data that you want. Meanwhile, the closed source tool doesn't support your desired action action either, but their file format is binary/compressed/encrypted/undocumented for nebulous "business reasons," so you end up spending fifteen hours pushing buttons in their GUI instead.
- collyw 6y ago"What if the vendor goes out of business without warning?" I think the open source equivalent is: "What if this library stops being maintained" Which I have encountered multiple times. Having the source code is useful, but most people don't have the time to add another open source library to the code that they need to maintain.
- lazylizard 6y agounless you're telecom? or fortune 500? most of the time its a "wait for next release". remainder is "known bug won't fix".