Wanted to get my 2 cents in here, hoping that this might get considered with some of the other big-picture refactoring efforts (#1524)

I find globals to be quite cumbersome, particularly the levels of forced taxonomy/hierarchy it imposes, just to expose simple data.

For example, out of the gate you're forced to make a global set, which means you will likely end up with some sort of meaningless catch-all like "General". Beyond that, you also need to create a tab grouping, which is probably going to be another meaningless label like "Content" or something.

I wouldn't be as opposed to this forced hierarchy if it were merely presentational, and you could change it and your content evolved. However, globals are called explicitly by their global set handle, so and reorganization is going to require a code refactoring.

As Craft 3 has embraced multi-site, one possible direction could be to treat Sites as elements, with the ability to add fields/field layouts, instead of "globals" being a totally separate concept (discussed here: #2790)

Related globals/global set issues:

• Feature Request: Allow me to sort the display order of Global sets #2682
• Add the ability to reorder Global sets #916
• FR: Custom Fields for Sites #2790