Programmer and mathematician. Problem solver. Lover of clean code, coffee, cycling, running and Italian food.
Kotlin, Java, Spock (Groovy), PHP, Angular, MariaDB, ...
/developer|entrepreneur/i
Always looking for new developer talent, even those with zero experience, as you never know who's got the potential to become a great developer.
Ruby doesn't lean too heavily on the dependency injection pattern, but it's still something you can see occur in many forms.
In other languages with a more formal implementation of this where it occurs is much more obvious, but in Ruby there's a very smooth gradient between light applications of this, like mixin methods from modules, to entire frameworks built around it, like Rails, and everything in-between.
So basically dependency injection is rarely forced on you, but it's there if you need it, and you can do it however you want.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Thank you for your comment.
I meant "DI is not really a thing" as in "in Ruby, DI is often not needed in the form of an entire framework as the backbone of your application".
Solargraph seems interesting, I will definitely look into that for code analysis!
Ruby doesn't lean too heavily on the dependency injection pattern, but it's still something you can see occur in many forms.
In other languages with a more formal implementation of this where it occurs is much more obvious, but in Ruby there's a very smooth gradient between light applications of this, like mixin methods from modules, to entire frameworks built around it, like Rails, and everything in-between.
So basically dependency injection is rarely forced on you, but it's there if you need it, and you can do it however you want.