@david_megginson @benBen Werdmuller

Yes, I agree. Though the diagram is too simple to capture it well, it is important to identify the forces that are at play, and the mechanics that drive them, and to subsequently monitor where you are and where you want to be in the future. So timely action can be taken to make corrective actions.

For the ecosystem for instance they might have identified a minimum set of standards to adopt, with which reasonably powerful "MVP's of the Semantic web" could be approximated with. And focus on strong library and tool support for that in multiple programming environments. Instead you enter a jungle of open stardards in various stages of completion, and good luck go figure it out. Also they might've focused on actual movement building. Far-reaching innovative standards - a new paradigm for the web - aren't adopted by the boardroom of a company, but are introduced by devs who get excited by what see and how they are empowered. And persuade management.

@david_megginson @benBen Werdmuller

Though with regards to progress, there's a difference in both approaches.

At the side you have inertia by the slow standardization process. But should they figure things out in a good way, eventually the ecosystem catches up and the inertia can quickly decrease.

While at side, since AS/AP remains stagnant, the ever increasing protocol decay and tech debt non-linearly increases inertia and progress. And on top of that, you are never done once you implemented the 'ad-hoc specs' of the installed base, and you have to account for continuous whack-a-mole development and maintenance burdens to fix breakages.

The AS/AP based fediverse devolves into effectively no interoperability, and a situation that is more comporative to NPM dependency hell.

0

If you have a fediverse account, you can quote this note from your own instance. Search https://social.coop/users/smallcircles/statuses/116114088567613180 on your instance and quote it. (Note that quoting is not supported in Mastodon.)