I agree with this, and it should be done. I started the process by creating the raku tag, but then ran out of privileges to complete it (I don't have enough perl6 tag-rep to complete the synonym.
The tag should be created raku and then existing perl6 questions should be merged in to raku, and then perl6 should be synonym-linked to raku. This will likely ...
There are a lot of sorts around, and their spelling varies. The rationale for the irregularity is likely that their names are irregular. Radix sort has a space between them, quicksort has not. It is like this on Stack Overflow as well.
(Note: Mast and I discussed this in chat this is a complete write up of my POV from this)
Salesforce's Developer Tools
I think that Salesforce has three major sections to their developer tools.
A language - Apex [W] [S]
REST APIs [S]
B2C Commerce Developer Sandbox API's
Einstein Prediction Service Scoring API
Einstein Vision and Einstein ...
Unification is great! But we don't need a new tag for that.
All questions mentioning a language by name:
Yes, this only covers less than half of the questions you list. Honestly, I think those are among the most important questions of your list.
Especially specific-language really sounds like it was made for (among others)...
We should tag them with scopelanguage-scope
Note: In case it's not been clear we're talking about Meta tags.
It should be noted that Mast's answer is in agreement with the groupings in the question. If the language-scope tag is added it would incorporate Mast's suggestion. It seems my explanation on why specific-language only fits on 11/28 questions was ...