weaver VS Resolver

> trying to hide distribution

The paper unfortunately hides that in reality you have to pass a context object in your RPC calls, hence there is no ambiguity whether you are calling a potentially remote object.

It's in the example on the project home page: https://serviceweaver.dev/

  // The "RPC" handler

Service Weaver is an open source programming framework from Google that allows you to write a Go application as a modular binary and deploy it as a set of connected microservices.

Boneless is a powerful tool that offers a wide range of features to facilitate application development. In this blog post, we will explore some essential tools that can be used in conjunction with Boneless: Service Weaver, Go Migrate, SQLC, and Fiber. Let's discover how these tools can boost productivity and efficiency in application development.

I assume you’re already aware of https://serviceweaver.dev/ Someone’s got to do it, so let that be Google.

If you're looking in to using a framework instead of doing it manually, I prefer Resolver over Swinject but both will work.

But, today, I use Resolver. And recommend others also use this. There are other approaches, but Resolver is quite good. It solves this problem. "Just pass stuff in to the constructor" isn't true dependency injection anyway (but it kinda works, it's just a huge mess).

You can achieve the concept as the environment in SwiftUI using protocols and Resolver https://github.com/hmlongco/Resolver

This isn't a full tutorial, but it's a great Swift dependency injection library with lots of information in its documentation: https://github.com/hmlongco/Resolver

I also suggest Resolver

Sounds ok, and for DI I can recommend this lib, works well and easy to use https://github.com/hmlongco/Resolver/

We’re using Resolver for dependency injection. Check it out: https://github.com/hmlongco/Resolver

Since multiple ViewModels need to access this data, I would avoid storing the data in a particular ViewModel—which should correlate only with a single, specific View—and instead implement this behavior in a third object (such as an AuthenticationService class). This way, both/any of your subsequent Views and ViewModels alike can all access that object as a single source of truth (by passing it around explicitly, putting it in the environment, or my favorite method: Resolver). Just remember to think about who should “own” data!