3 ms·
Disclosure: I work for Red Hat I think you're missing the real value here of the support model and services a company like Red Hat can provide to large orgs.
by freedomben 7y ago
Disclosure: I work for Red Hat
I think you're missing the real value here of the support model and services a company like Red Hat can provide to large orgs.
It's not about having support for every package, it's more about having others do the hard, expensive work of presenting you a portfolio of projects known to work well together, so you can focus on adding your own business value rather than spending hours duplicating effort from others and debugging arcane issues.
To some extent you can't out-source everything (and I personally wouldn't recommend that. I think having some in-house experts is really important), but not everybody should roll their own OS, DB, container orchestration, etc.[1], and finding consistent options that work together can be difficult when you have huge, diverse, engineering departments with different values/priorities.
I don't disagree with you: I think contributions in either code or donations are a great way to support FOSS projects. I just think there is also a lot of business value in the support contract style method, because you're not just buying insurance, you're buying real value in the form of somebody presenting you with a portfolio of disparate open source projects that have been integrated and tested together.
[1] Note I'm not talking about "React v. Vue" which I agree support wouldn't make sense for.
- smichel17 7y agoTangent: I appreciate when people put conflict of interest disclosures at the top of their post rather than the end. Thank you.
- mmsimanga 7y agoAs a developer running a couple of servers I understand your point. I used to love updating to the latest version of all software I was using. Now I am quite happy to use what my Linux distro packages. The stability is the best feature.
- dnautics 7y agoThanks for the insight. How might someone in a position to spin up services for this be able to think about capturing this sort of a market? I work at a DL/ML hardware company; and many here on HN would know that packaging DL libraries correctly is a nightmare and a half. In fact a good chunk of our value prop is offering an open source pre-baked bundle. It's great (and I've deployed it on some friends' machines and they love it) but it's, let's say three-quarter-baked and moving it into a "fully supported" model with domain-specific expertise isn't something that our company has figured out how to transition into (also not easy given our company is really small), and given business strategy and software strategy are independently difficult enough problems. Do you (or any others) have any suggestions?
- mooreds 7y ago> Thanks for the insight. How might someone in a position to spin up services for this be able to think about capturing this sort of a market? Obligatory (from 2014) "Why There Will Never Be Another RedHat: The Economics Of Open Source": https://techcrunch.com/2014/02/13/please-dont-tell-me-you-want-to-be-the-next-red-hat/ https://techcrunch.com/2014/02/13/please-dont-tell-me-you-wa...
- dnautics 7y agoThanks for the link!! Luckily it's not the only path for growth... As I mentioned we're a hardware company so it's more like we want to wind up as a Dell (or in a worse scenario, IBM, which isn't too shabby)
- jabl 7y agoAs the article the grandparent links to shows, RH is maybe the singular example of a big successful pure OSS software company. It seems almost all other big successful OSS companies have adopted some kind of 'hybrid' strategy such as open core, many after first unsuccessfully trying to emulate RH. To a hw company, I think the issue of how to monetize SW is to some extent clearer as well as pretty different than for a pure sw company. You're selling a tangible physical product, but customers are not interested in the raw hw but the complete package of hw plus supporting sw (drivers, SDK, whatever) + support. So you have to choose what is the appropriate model for you. E.g. - Use profits from HW sales to develop OSS that makes the HW more useful to customers, and thus increases HW sales. For instance, one argument in favor of this would be that drivers included in the upstream kernel and user-space software in distros makes it easier for customers to use your HW. And you'll get OSS brownie points which might also help drive sales. - Or make the SW free but not OSS, in case you're worried that your competitors could just take your OSS and use it with their HW. - Or make proprietary SW that you sell in addition to the HW. I'm not sure customers care about how you split the total bill they're paying, and free (as in beer) software is certainly a lot easier to deal with for customers (e.g. license hassles). But again, it depends. - Oh, and another potential advantage of the OSS SW model is the 'commoditize your complement' angle (do a web search on that phrase if your unfamiliar with it). tl;dr You can use OSS SW to undercut a pure SW competitor, as your income is protected by your 'HW moat'.
- freeone3000 7y agoOkay, but CentOS offers the same thing, sans contract. Why bother paying when you can get the same thing, with no support, for free?
- froh 7y agoRedHat (or Ubuntu let's or SUSE Linux enterprise) have reactive support: call them if something goes wrong, and the, have proactive collaboration with paying customers. If you think you don't need that: use free riding flavours i.e. centos/ SUSE leap/... Tech support can tell by looking at the system if you are a paying customer or a free rider. And sales can look at the download numbers and management servers if your installed base is what you claim it is.
- freedomben 7y agoRHEL (CentOS) is only a small piece of what Red Hat offers. If all you want is a base RHEL system (that can be a week or two behind on non-security patches but is otherwise the same), and you don't need any support, then yeah I'd do that (and I do in fact. I use CentOS for personal stuff all time). Since all of Red Hat's stuff is open source, you could install them all individually just fine. I think of Red Hat as more of a competitor to cloud companies than to Linux companies. A lot of what we do is help people build their own private clouds on the hardware they own. RHEL is at the foundation of course, but RHEL is very rarely the end goal of the customer. If you are doing this at scale, you're going to end up paying way more in salary to employ people to do it than you would if you just went with Red Hat support. And since early in an effort you need more people, you would either have to lay people off or find new jobs for them. I often swoop in and knock out tasks in hours that would take the company's infrastructure/SRE teams days or weeks to do, because I've done it a lot and I know what I'm doing. Its also less likely that I'll make a configuration error that exposes itself in prod, simply because I've already made those errors in the past and learned from that mistake. And when I do screw it up (which is a very, very, rare occurrence ;-) ), the company isn't scrambling to fix it. They call up support and we get it fixed ASAP. Again it's not for everyone, but it is for some people. I usually find that buying Red Hat saves a lot of money rather than costing money, which is why so many big companies do buy us.
- prepend 7y agoI think I see the value of RedHat, but I don’t think it makes sense for every project to have a RedHat equivalent.