The default .conf file would of course use a sane organization (ex. alphabetical)

Alphabetical means a long menu to move the (mouse) cursor through. I think we can make categories work. The Pascal style group is not intuitive, particularly Lua and Ruby, I don't know the others. For C style Go and Rust are not intuitive (e.g. function and variable declarations), and even JS and Java are unexpected there. Instead I would like:

• C family - C, C++, Objective-C, C#, D
• Static - Other statically typed
• Dynamic - Perl, Python, Ruby, JS - these are general purpose rather than mainly functional
• Functional - as @codebrainz suggested
• Scripting - Batch, PowerShell, Shell; Make, NSIS - anything that runs programs by a command line and is not used as a general purpose dynamic language
• Markup, Misc - as present

I don't see a problem with some categories being more specific, e.g. having C family separate from Static. That was the philosophy behind having the Programming vs Scripting divide - it was not implying that scripting is not programming, just providing a way to group languages in an obvious place, scripting is more specific than programming.

Note that YAML and JSON should go under Markup but are in Misc ATM. Markup could be renamed something like Structured Text, but markup WFM.

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