19
votes
if ( [conditions].isGoodTag() ) { return "keep" } else { return "burninate" }
Really, I think that the tag is really broad.
We have enough tags that we don't need one for Conditions.
(almost)All code has conditions in it for one thing or another. I really don't think that ...

MalachiMod
- 28.6k
17
votes
.net to the core
I'm going to defend all these tags, because after thinking about it, I think they do provide value.
First and foremost: .net / .net-core are not universal/compatible. Just because something works in ....
13
votes
for (post in [loop]) { post.tagMoreAppropriately(); }
Burnination is probably fine and the iterator tag probably suffices for the examples my previous answer references.
The tag is pretty terrible.
11
votes
Do we even need to keep following [meta-tag:site-policy]?
Yes, we should keep it
Fixables
First up, the following issues you have pointed out can be fixed (and I am in the process of doing that):
it will have a tag wiki soon
the excerpt will be clarified to ...
9
votes
Should we [join] this tag with the other burninated ones?
No, your statement that join is related to sql is a faulty assumption.
There are also questions about performing joins with excel, csv, pandas, or just joining data the hard way in regular ...
9
votes
Accepted
Should we put [scope] down our scope?
On Code Review tags are more useful when they refer to:
The features that the code on question is implementing i.e linked-list
The context that question is originated from i.e programming-challenge
...
7
votes
Do we even need to keep following [meta-tag:site-policy]?
I agree.
This tag is redundant in it's current state. If it had a different purpose originally, I suggest we restore that purpose. If it didn't, we should possibly get rid of it.

MastMod
- 13.1k
7
votes
Burninate [heuristic]
One-off tags are automatically deleted after six months, according to the answer I got here on Meta Stack Exchange. So unless somebody else uses the tag meanwhile, there's no need to take action.
7
votes
Would burninating [performance] bring good performance?
I see three main trade-offs in most code.
Performance
Memory usage
Readability
And so when a question is posted on Code Review I think they want a trade off of all three. And so I normally try to ...
PeilonrayzMod
- 42.7k
6
votes
Should we cast away [casting]?
I'm not so sure. Neither of those two reasons is a solid justification for eliminating a tag.
Applicability to multiple languages is a poor criterion. By that logic, we should eliminate fizzbuzz.
...
6
votes
Does the [converting] tag provide any value?
Watering down
I think we are sometimes too lenient on our tagging.
For example, a translator or type conversion shouldn't be tagged conversion.
The former whilst you are changing the input, it's not ...
PeilonrayzMod
- 42.7k
5
votes
Accepted
Normalizing [data-structures]?
I agree with abolishing data-structures.
The tag can currently be used in three ways:
Redundantly along with some other tag, such as tree or stack. I think that in these cases, data-structures adds ...
4
votes
for (post in [loop]) { post.tagMoreAppropriately(); }
Burnination is not fine.
I can think of at least two specific examples where the loop tag is more than appropriate:
A general iterator to replace "non-standard" C-style for loops
Swift replacement ...
3
votes
Would burninating [performance] bring good performance?
There are 344 followers of the performance tag.
Are there experts in performance? Yes.
Is it likely that a question tagged performance gets extra attention from specific users? Yes.
It should stay.
2
votes
Accepted
if ( [conditions].isGoodTag() ) { return "keep" } else { return "burninate" }
Even with Trogdor's assistance, conditions stayed alive due to its Horcrux: the synonymized ternary-operator still tagged with some questions. With no soul pieces questions remaining, conditions will ...
2
votes
Shall we keep shelling out questions for [shell]?
I think this tag has a value. It can help users proficient in shell-scripting (in all its forms) to find questions that are doing shell scripting.
There's some common standard errors in shellscripts ...
2
votes
.net to the core
I propose we create a .net-core tag for the overarching framework, and replace:
entity-framework-core with .net-coreentity-framework
asp.net-core with .net-coreasp.net
1
vote
Should we [join] this tag with the other burninated ones?
Burn it.
Pretty much all SQL queries use joins in one form or another. I think that having sql is on its own sufficient and it should be assumed that any SQL question could have joins, making the use ...
Only top scored, non community-wiki answers of a minimum length are eligible
Related Tags
discussion × 53tags × 53
burninate-request × 53
status-completed × 29
status-declined × 5
meta × 2
scope × 1
feature-request × 1
synonym-request × 1
specific-language × 1
status-planned × 1