I'm familiar with them.

These are projects sitting years, maybe even a decade, away from maturity. IF web standards and capabilities don't change at all over the next 5-10 years.

Hopefully that puts this into perspective. These are really cool projects, but without a massive influx of engineering effort and organization, they will likely be perpetually, hopelessly, behind the standard rate of change required of browsers. Nevermind meeting the current standards of performance, security, observability, ecosystem, user and developer experience.

It's always good to check in on these projects yearly, see how it's going, see if they are accelerating or slowing down. Eventually one of them will take off, and potentially leech resources from other similar projects.

Though, the nature of FOSS is that 1000 people will work on 200 different projects all trying to do the same thing, instead of combining and organizing efforts to go after the same unified goal.

This isn't really a statement of fault but rather a statement of reality. Without dedicated full-time organization, this is usually how scattered resources solve problems. Which is a core problem here in that dedicated organization to rapidly grow the engineering effort for a particular project usually requires funding and full-time employees. To both market it to engineers as an interesting project, mature documentation and DevX, mature the onboarding experience for devs, and to handle the organizational aspects of distributing said work.