Because of that stake, they want an "exit" in some form, and the drive to that exit will pave the road to user-hostile software and make it the path of least resistance.
One note: technically my software isn't quite Open Source; it's source available. [0]
I will have my first release in less than two months, hopefully. It will include a scripting language and a build system.
If the language gets interest, I'll expand it and build the standard library.
If the build system gets interest, I will expand it. The end goal is Nix for mere mortals.
If neither gets interest, I will have to move to my next idea: VCS with project management and that handles large, binary files.
Beyond that, we'll see.
I have a business website, but not yet for those projects. I will at release, including tutorials.
You can read an old commit of design docs at [1], [2], and [3].
It's just me; I want to run my business like Hwaci, the SQLite guys. That also reduces overhead and will let me provide excellent support [4] for paying clients.
[0]: https://gavinhoward.com/2023/12/is-source-available-really-t...
[1]: https://git.yzena.com/Yzena/Yc/src/branch/master/docs/yao
[2]: https://git.yzena.com/Yzena/Yc/src/branch/master/docs/rig
[3]: https://git.yzena.com/Yzena/Yc/src/branch/master/docs/yar
However, there are rumblings that standards and liability will be imposed on the industry.
In that case, I would be well-positioned as someone who could accept that liability for a price. Your run-of-the-mill build system created by volunteers? Not so much.