It’s good to develop standards even if the vast majority of people won’t adopt them, so the small minority who care build on one good protocol instead of many bad ones.
Ex: ActivityPub. You have many different people making social networks, and they all can interact with each other. These “many people” are a tiny fraction of those who use HTTP, but their numbers are enough to form many thriving communities.
At the same time, ActivityPub and its services (Mastodon, Lemmy) have serious flaws in discoverability, permanence, and inefficiency. If someone were to invent a new protocol (perhaps AT, perhaps “ActivityPub 2.0” or “ActivityPub+”, perhaps something else) with a way to interop with and migrate old data, it could be very beneficial to those communities.
Furthermore, one day the world may change enough for a new standard to take hold. And perhaps it will be sudden, and/or developing a “good standard” takes a long time, so we wouldn’t have had time to if we didn’t start on a random day like today.
> It’s good to develop standards even if the vast majority of people won’t adopt them
I'm not sure I agree that his standards are that good though. I mean, there's a limited number of standards that the community in general can pay attention to, and you still have some responsibility in not channeling energy into something that can't be upgraded to meet the unexpected needs of the future.