Skip to main content
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 ...
Malachi's user avatar
  • 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 ....
Der Kommissar's user avatar
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.
nhgrif's user avatar
  • 25.3k
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 ...
200_success's user avatar
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.
Glorfindel's user avatar
  • 1,089
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 ...
Peilonrayz's user avatar
  • 43.4k
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 ...
200_success's user avatar
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 ...
nhgrif's user avatar
  • 25.3k
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.
Simon Forsberg's user avatar
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 ...
Vogel612's user avatar
  • 25.2k
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
Mathieu Guindon's user avatar
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 ...
Jamal's user avatar
  • 34.9k
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 ...
Phrancis's user avatar
  • 20.4k

Only top scored, non community-wiki answers of a minimum length are eligible