I think this is where Apple's walled-garden approach is actively harming the growth and resilience of their operating system.
Unlike GNU/Linux, only Apple's in-company devs get to work on the proprietary code base, to build features based on a small number of decision-makers, and test them before release. Questionable decisions in the core don't get questioned by a wider community of devs before they get released to the public.
In Jobs' days, this approach might have worked better due to (maybe smaller code base and) higher quality and dedication of their internal dev teams.
Open-sourcing macOS maybe wishful thinking, but it's not an unreasonable idea, considering it's not their main money-maker (anymore?). In my opinion, this would vastly improve its future development, active participation by motivated community, and quality control.
Unlike GNU/Linux, only Apple's in-company devs get to work on the proprietary code base, to build features based on a small number of decision-makers, and test them before release. Questionable decisions in the core don't get questioned by a wider community of devs before they get released to the public.
In Jobs' days, this approach might have worked better due to (maybe smaller code base and) higher quality and dedication of their internal dev teams.
Open-sourcing macOS maybe wishful thinking, but it's not an unreasonable idea, considering it's not their main money-maker (anymore?). In my opinion, this would vastly improve its future development, active participation by motivated community, and quality control.