Slide VS Dagger2

Thank you kind stranger! I opened https://github.com/Haptic-Apps/Slide/issues/3485 with slightly different instructions (shaved off a couple of steps). For example Step 1 can be skipped by doing clone from repo in step 4.

TIL that Slide is also open source: https://github.com/Haptic-Apps/Slide

So long Slide and Infinity, ill see you again in the Fediverse

I didn't actually hear that they were doing API changes? I use Slide, so I guess for me one day in the future Reddit will just stop working.

Slide: intended for everyone, but Its lead developer was immediately open to addressing accessibility concerns, during the beta process, and u/MostlyBlindGamer was able to contribute several fixes for the TalkBack screen reader.

Which would be good open source 3rd party apps to test with? I found a couple of mobile apps, like https://github.com/Docile-Alligator/Infinity-For-Reddit and https://github.com/Haptic-Apps/Slide

FYI, Infinity and Slide are solid reddit apps and both open-source. I still prefer RIF, but in case your wish doesn't come true there are already at least two pretty good options.

I used to use Slide. Switched to Infinity after seeing it promoted on F-Droid. Both are great (with a preference for Infinity) and I will stop using reddit on mobile because I refuse to use their mobile app.

This project will be on indefinite hiatus for the foreseeable future, and may not be maintained. Updates are not guaranteed. See here for details.

There used to be a thing called "releasable references" which was that. It was removed, though: https://github.com/google/dagger/issues/1117

As said in the title, we will focus on the dependency inversion principle and one of its application : dependency injection. For production-ready applications, it would be better to rely on a framework and not implement its own container. For it, the java ecosystem have 3 frameworks available : Spring, Guice and Dagger.

At Reddit, we use Dagger 2 for handling dependency injection (DI) in our Android application. As we’ve scaled the application over the years, we’ve accrued a bit of technical debt in how we have approached this problem.

Confusing. I initially thought someone ported the Dagger DI framework to Python: https://dagger.dev/

I'm currently using Dagger and Anvil for my DI needs. It's been working really well, especially around what Anvil permits in terms of multibindings defined on the type declaration rather than in a module. For example:

Great job, I have been waiting for this feature/fix for a long time https://github.com/google/dagger/issues/2328

Dagger