7
\$\begingroup\$

A tag was recently created for , which is an IoC container. The question that created this tag is also correctly tagged with .

A long, long time ago I wanted to create a tag for (another IoC container) but I didn't have enough rep back then, and was deemed to encompass it properly. Turns out was also created recently, on another Ninject-specific question.

While the specific IoC container chosen by the OP has zero importance as far as the application code is concerned (if DI is implemented correctly that is), the shape and content of an application's composition root (where the dependencies are resolved and the constructors are called and injected with the IoC-container-provided instances) and of its infrastructure code, is highly specific to the selected IoC container.

Therefore, I believe is not sufficient to properly tag a DI question that features code that is specific to an IoC container, and reviewers familiar with DI but only with certain containers might want to review questions but skip or ignore questions.

Is there a consensus that IoC container tags should be allowed to exist, or we should edit them out and simply use ?

\$\endgroup\$
2
  • 5
    \$\begingroup\$ Can you please repeat all that in English? \$\endgroup\$
    – rolfl
    Mar 12, 2014 at 17:19
  • 1
    \$\begingroup\$ @rolfl IoC => Inversion of Control \$\endgroup\$
    – Mathieu Guindon
    Mar 12, 2014 at 17:21

1 Answer 1

Reset to default
4
\$\begingroup\$

Both and currently only feature one question each. This supports my line of thought that DI isn't so pervasive that subdivision into different frameworks could make sense here ( currently has 42 questions, which I take as a good omen).

Other design patterns like have seen such widespread use that a tag for each major framework makes sense.

DI isn't there yet, so I'd support retagging and removal of the offending minor tags.

\$\endgroup\$
3
  • \$\begingroup\$ OTOH if I were to go through all 42 [dependency-injection] questions, there'd probably be a bunch that would get a [ninject] tag, and another bunch that would get an [autofac] tag, and probably another bunch that would get another IoC container's tag. \$\endgroup\$
    – Mathieu Guindon
    Mar 12, 2014 at 17:31
  • 1
    \$\begingroup\$ @Mat'sMug very good point, there are 8 DI questions containing “ninject” and 4 for autofac \$\endgroup\$
    – amon
    Mar 12, 2014 at 17:33
  • 1
    \$\begingroup\$ If the policy is to remove IoC container tags until there are enough questions with those tags to show that they're widely used... I think I see a problem there \$\endgroup\$
    – Ben Aaronson
    Mar 15, 2014 at 15:26

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .