We should consider listing extensions in alphabetical order in the README instead of the current "numerical" order (based on date).
The most common issue we encounter when merging PRs to this repo is a merge conflict in the README when two extensions each add themselves as the last item in the list. Switching to alphabetical order would not completely eliminate this issue in theory, but it should make it much less likely to occur in practice.
If I am searching for an extension by name it is obviously much easier to find if the list is in alphabetical order. Currently, I almost always need to use my browser's search feature to find the extension I am looking for.
Listing extensions in alphabetical order also makes it more likely that related extensions will be listed together, which may help discoverability.
Some Khronos APIs assign numerical IDs to extensions (I believe OpenGL still does, maybe others), but SPIR-V does not, so the number of the extension in the list does not have any specific meaning.
We can always use git history if needed, to reconstruct the order extensions were added to the README and this repo.
We should consider listing extensions in alphabetical order in the README instead of the current "numerical" order (based on date).