It might be a bit controversial notion. But when I try to look for extensions say for completion framework there are many available and I used ido and then moved to ivy. I knew helm existed and is much more powerful in terms of feature-set, but never used it.
I read that emacs can report on keyboard usage (I think from xahlee’s posts). Can it be repurposed to monitor which extensions are used often in users setup and they can share that report if they wish to public say via melpa like services. I suppose that melpa downloads can be used as a measure of usage.
From a technical perspective maybe this is achievable through a mix of dribble files (see
open-dribble-file) and simple heuristics for guessing which functions are associated with a package (see here maybe?)I agree with others in that this might be a flawed way of measuring usage, but I think it still would be somewhat interesting to see those stats for fun!
Also after a bit more thought I think implementing this would be useful for a totally different purpose: programmatically finding underused keybindings/functions could help a lot with discoverability!