Explore >> Select a destination
|
You are here 
|
software.rajivprab.com | ||
| | | | |
jmmv.dev
|
|
| | | | | Dependency injection is one of my favorite design patterns to develop highly-testable and modular code. Unfortunately, applying this pattern by taking Rust traits as arguments to public functions has unintended consequences on the visibility of private symbols. If you are not careful, most of your crate-internal APIs might need to become public just because you needed to parameterize a function with a trait. Let's look at why this happens and what we can do about it. | |
| | | | |
publicobject.com
|
|
| | | | | You can do dependency injection (DI) manually or with a library. Constructing your applications dependency graph by hand is a cute exercise but not practical beyond toy examples. Youll eventually find yourself extracting the repetitive manual DI code into your own bespoke library, one thats likely to | |
| | | | |
blog.kotzilla.io
|
|
| | | | | A look back at Koin's 2024 milestones, incl. Koin 4.0 release, our performance benchmark against Dagger Hilt, and a peek at upcoming Koin Injellij Plugin. | |
| | | | |
alexene.dev
|
|
| | | Most WebAssembly tutorials and examples you will find online focus on using it inside the browser in order to accelerate various functionality of a website or web app. However, there is an area where WebAssembly is really powerful but not talked too much about: outside the browser usage scenarios. That is what we'll focus on in this series of posts. | ||
