Resolving Dependencies Helpers

[@KeganVanSickle]

This is actually a "complaint" I have with Laravel. I love Laravel, don't get me wrong, but I don't like how there are so many ways to do the same thing. I like it when frameworks are opinionated. Either it works, or it doesn't. Less room for errors and hidden bugs and all "magic" under the hood.

In my opinion, “resolve()” is clearly the best choice as it does what its name promises

[@LaravelPHP]

😘

[@ruslansteiger]

I prefer "resolve" as well, Adrian. 🤝
It's much clearer what you want to do and less confusing for new developers. 😊

[@Cyapow]

But do you prefer it over dependency injection in a function / class? Im curious which is the best option. I usually go the DI route

[@WomboCombo950]

How this deal with overloading, lets say that we have a lot of instruction do this lead us to big request start time ?

[@mahdibagheri71]

I typically use app(abstract) or utilize in function controller.

[@ali_raza]

Thanks for showing the ease way

[@martinbean]

If you use dependency injection then this whole debate becomes a non-issue.

[@prymiee]

bit of a `app(abstract)` fellow myself :)

[@Hypergraph]

hey, your hat annoys me so i unsubscribed from laravel. best decision i've ever made.

[@1234matthewjohnson]

hahha gold