I've noticed a lot of discussions lately about Dependency Injection (DI) within JavaScript. Coming from a background in Java and PHP, where DI is widely adopted, it seems to me that not having DI in JavaScript is a significant limitation that leads to various issues. I recently shared a blog post that outlines my thoughts on using DI with JavaScript classes, but I faced quite a bit of backlash for it being considered overly complex. As a follow-up, I've created another post that explores how to implement DI in a functional programming style with JavaScript. I'm curious to know if others think there's a future where DI can coexist effectively with JavaScript. What are your thoughts?
2 Answers
I totally see the value in DI patterns, as they help in managing dependencies effectively. However, I've noticed that some languages add so much 'magic' to DI that it becomes unclear where dependencies are created. I've had bad experiences with libraries like typedi. Maybe sticking to simpler implementations could serve better.
Agreed! I've found that solutions like tsyringe work great for basic needs while keeping things less convoluted.
Honestly, I question the necessity of DI in JS or TypeScript. Most of the time, modules and higher-order functions suffice. It feels like DI adds layers we don’t actually need.
Exactly! The Java structure might demand DI, but JS does a great job with its own module system.
Well, I think for testing purposes and maintainability, DI can still hold value, even in a JavaScript context.
That's true! The idea of DI is wonderful, but if it becomes overly complicated, it's like trying to fix a puzzle that doesn't make sense.