it means one submenu level "a-f", "g-m", "n-p", "q-z"

This is hard to internalise, learning the arbitrary ranges. If I want JS, I can't instantly know which sub menu it is. It doesn't take long though, but it's nice to avoid this for UX.

don't need to be a "programming language nerd" to guess a category

My categories are clearer than Matthews, but yes probably some users won't know about static Vs dynamic typing - they would hopefully pick up the distinction by inspecting the contents. Or we could keep the status quo and add C Family and Functional. These categories are known by their users.

don't hard code some set of groups,

I don't think users will bother to redefine these groups, why support that? Also did you see my 2nd comment about user-set ungrouped filetypes?

for gods sake
its just plain arrogance on the developers part

Please can we avoid emotive language and stick to constructive criticism? I'm anxious, my heart is beating fast as I type this. It just makes collaboration more difficult.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.