This isn't an answer, but rather an appraisal of the situation and analysis
From earlier comments
Yeah, sounds like it could be a good idea. However, is there really no difference between slicer and slicing? I can't think of any differences, off the top of my head - unless the former is about the software and the latter is the process. I see that slicer has no tag info, defining how the tag is meant to be used, whereas slicing does have a clear tag usage.
More importantly, leading on from that, are the tagged questions themselves tagged "correctly"?
Do the questions in the two tag groups have different leanings, i.e. those tagged slicing are more process oriented and those tagged slicer are more software oriented?
At first look
As stated in the question, there are currently 204 slicing questions and 6 slicer questions.
The missing tag info for slicer is easy to add - anyone can do so. I don't know why it wasn't added when the tag was added (more about this below, see Further Analysis).
Whilst having two tags seems to make sense, the questions should be checked to see that they have been tagged correctly (i.e. software or process oriented). This isn't an insurmountable task, although 204 is a bit of a chore. It's been done before, see the maker and model meta question, Tag Maintenance Summer 2019.
However, if while checking whether the questions have been tagged correctly, it then becomes a bit of a headache actually distinguishing the questions correctly - that is to say, determining whether slicing or slicer (or even both!) applies - then maybe, one should be the synonym of the other.
Further analysis
Looking at the dates of the two groups of questions, it seems that slicer is actually a (relatively) recent tag, presumably introduced in May 2021 with this question, How to fix zits and blobs caused by Cura? , which seems to be reasonable as the question is about Cura, rather than slicing, in general. However, I might be wrong in thinking this, I don't know - maybe slicing would have still be sufficient tag for this question, in which case, the whole slicer issue started with this question.
However, further checking reveals that slicer was only added to that question, a month ago by this edit. So, really, this question could be retagged to slicing without issue, as it has only had the (alleged) "wrong" tag for a few weeks.
That leaves 5 remaining slicer questions, and then the next oldest question tagged slicer is Are there any slicers that use anti-aliasing (such as FXAA) for higher quality thumbnail generation?, which is where and when the slicer tag was introduced - 30 Nov 2023 - so it really is a late addition. Interestingly, the same user edited the previous, older question to add the slicer.
Again, this question could be considered to be about slicers rather than slicing, but whether that merits having a new tag, that could potentially cause endless confusion, and mis-tagging, down the line.
The other four remaining questions were tagged as slicer by their respective OPs, and while at least two of them (Does FreeCAD produce a wrong stl for slicer software? and Effect of top thickness on print with bumps on top) could be considered correctly tagged as slicer, IMHO moving them to slicing wouldn't harm the questions. The other two (Encountering some weird layer gaps on the last few lines of a particular print and Deformed 45 deg angle on outer wall) look to have been incorrectly tagged, and slicing would be more appropriate.
Update: I have retagged these last four questions as slicing
Was there a need for a new "slicer" tag?
I would like to ask the OP, who introduced the slicer tag, their reasoning for doing so, as well as:
- Why no tag info was added for slicer, in order to distinguish its use from that of slicing?
- Was the existing slicing deemed not to be appropriate, if so, why not?
I would suggest that we wait for an answer/response to those questions, before we even consider blatting the slicer tag (or creating a synonym).
There may be a legitimate reason to have a distinct tag, especially if there is a need and desire to separate software from process.
Moving forward
It may be decided by the community that a distinction is required and hence the need for two tags.
However, if it is determined that there isn't a real need for a new tag, then we have two options:
This latter option seems the easiest option and just returns everything to the way that they were prior to slicer having been introduced.
slicer
has no tag info, defining how the tag is meant to be used, whereasslicing
does have a clear tag usage. More importantly, leading on from that, are the tagged questions themselves tagged "correctly"? $\endgroup$