Inversifyjs: Not really clear why someone should use Inversify. Could you elaborate?

[AriaFallah]

I don't mean that in a rude way, but just as someone who's stumbled upon the repo it seems like a lot of decorum for simply passing parameters around.

Your README says

InversifyJS is a tool that helps JavaScript developers to write code with a good OO design.

but really doesn't go into depth much after that.

I think it'd really be helpful if you had some examples of how Inversify compares to the alternatives. To me, not saying it's right as it's probably wrong, I feel like everything inversify does, I could do without it, and your README does nothing to convince me otherwise. I feel like it really only caters to people who have used DI before.

So to follow that up. Why, specifically, should I use inversify? What common problems in JS does it solve that I couldn't solve without it?

[remojansen]

I will try to document it better in the future (my priority right now is the 2.0 release candidate) but for the moment you can refer to some of my blog posts:

• The current state of dependency inversion in JavaScript
• About object-oriented design and the “class” & “extends” keywords in TypeScript / ES6

IoC containers is somehow controversial and not everyone feels like it is something that they need. If you feel like you need an IoC container then I would like InversifyJS to be the best but if you don't want too use it that is cool too. My personal point of view is that if you code using an OOP style InversifyJS will help. If you are using a FP style then you probably don't need it.

[AriaFallah]

Alright thanks! I'll take a look.

[AriaFallah]

@remojansen both blog posts were exactly what I wanted. Really well written. You should put them at the top of the README or something.

[remojansen]

Thanks! I have plans to create page about "motivation" in the wiki. I will add the links there :)