Other problem is being the _sole_ Patreon.

Many people think that the best thing for projects like this is to have as many entities involved as possible. Anything that is controlled by single entity is bound to forget the needs of others.

For example: neither Mozilla nor Amazon might have Embedded Systems as a core interest, so they will forget about it and might accidently make decisions that ate bad for this use cases. If you also have ARM, Microcontroller vendors and so on on board, they will make sure that this topic isn't overlooked.

>> Anything that is controlled by single entity is bound to forget the needs of others.

That is perhaps the biggest concern.

When a large tech company controls governance, their needs and priorities come first.

We have seen similar concerns with other programming languages in the past: Java (Sun / Oracle), Go (Google), Swift (Apple).

Exclusive or dominant control is not necessarily bad (depends on how transparently the governance process runs and who is involved), but it can severely limit the programming language community's effect and leave the needs of some groups unfulfilled.

The issue was with Mozilla bring the only patron. Also, your sentimrnt about Firefox os not shared by many here.

I don't agree at all that they are managing the Firefox project well. See the evolution of Firefox's market share over the last decade.

Apache is where projects go to die. So, probably not.

> Apache is where projects go to die.

I thought that was CA? Oh wait, no, that's where they go after they're dead.