Yes, I was referring to RedHat. It is built around open source, but with the resources of a commercial enterprise that you can rely on. While many open source products have almost equivalent support of commercial products (sometimes even better), it’s a fallacy to equate the two.
There is a fascinating take on this topic in this write-up:
The writer attends a conference on an EU initiative to have an alternative to big cloud providers. The initiative produced a very large proposal and many papers and concluded with
“We created all the concepts and ideas and we’re now looking for the Open Source community to build the software for an autonomous European Cloud”
When the author asked the presenter what funding was associated, she was confused and responded “No, the Open Source community should implement it now.” When asked if she knew how open source worked or ever written parts of it, or contributed, her answer was ‘No’.
I think open source is a fascinating concept. It does empower developers and provides a counterweight to all software roadmaps being controlled by for profit enterprises. It does allow everyone to benefit from the opportunities of software without being rich themselves. That’s a huge win for society.
But I find the reliance of the commercial enterprises and commercial users on the open source community to provide much of the critical infrastructure as misguided. Yes, many of these companies do in fact fund some of the effort or contribute head-count. Which has somewhat perverted the whole concept of open source, as it’s again at the whim of big corporations. But nevertheless, that was never the intention or the goal.
A product like Flame and a company like ADSK should first and foremost support a commercial edition of Unix (as it did with Irix), or at a minimum a commercially supported open source project, like RedHat. And big studios should use that version of OS.
It is a nice to have that Rocky exists as an equivalent free version, and that allows freelancers, students, and small businesses to optimize cost and benefit from the flexibility of a Unix environment.
So ADSK should first offer a RedHat version of Flame, and then also a Rocky version of Flame. It could of course also offer an actual commercial version, but then duality would be more complex.
RedHat is built on top of an open source OS. While I don’t know the full breakdown, I do assume that a portion of the revenue and effort logically also flows into the improvement and maintenance of the code base, it’s not just a resale operation by the nature of it.
Keep in mind that you are paying for MacOS as a commercial flavor of Unix. Not as a separate line item, but implicitly via your Mac hardware purchase. It was not long ago that Windows was an OS that was shrink-wrapped software that just came pre-installed by the OEM. In my software career I’ve worked on HP-UX as an engineer, and used SunOS, AIX, and other flavors over the years. I worked on OS kernels before Linux existed - your choices were FreeBSD or SystemV.
Another way to illustrate the dichotomy of open source and free software. It does not take much to get artists - starting with stills photographers who are the worst in this regard, but I’ll include Flame artists and anyone in between in this grouping to go on that ‘you shall not work for free’ and that any client that wants you to work ‘for exposure’ or otherwise undercuts your fair rate is a cheat, and worse. They all demand fair pay for the valuable work they do. And they should.
But doing so while using the completely open source Firefox browser and many other open source tools who are the sweat equity of software engineers, who are artists in their own field, is a contradiction extra-ordinaire. And most do so with full ignorance of the matter.
While many here are righfully appreciative of the contributions made in the form matchbox shaders, python scripts for ML timewarp, etc. you do find the occasional comment that ‘expects’ these products to exist. Such expectation is misplaced. These are free contributions.
And any commercial enterprise, from the companies to the studios, should be the last one to expect such free contributions and use them readily. And there have been multiple comments over the months that were critical ADSK for Timewarp ML having to be a community solution rather than an officially developed solution. Rightfully so.
I write all of this as someone who has spent 15 years of my working years as a software engineer, and now 15 years as an artist in several different roles, and run my own business. Thus I have skin in the game on both sides.