1,206 karma · joined March 24, 2017
reach me at sam at the domain mentioned above, or github.com/sgammon
> > can’t live up to owning it.
> ?
Dagger, the DI framework, is very popular, supported by Google, and the primary way to do DI on Android (for many). It is not going anywhere. It is unlikely that this tool or product will create a bigger audience. Therefore, it might never "live up to the name," compared to the benchmark set by current Dagger. It's a simple concept.
Android is the most popular operating system on earth. Names can overlap but you shouldn’t choose one where you can’t live up to owning it.
You could add your own instead, explaining how things work?
> It's possible to ask AI to write code and then read the code yourself
Sure, but then it would not be vibecoding.
High performance, polyglot, AI-native runtime. We are in San Francisco, but work remote. Kotlin and Rust.
if such a thing were possible, thread coordination would not have those issues in the first place
i used to think this way, and then i tried it, and i have to admit it's pretty good.
think of all the complexity on the other side of running a stable multi-regional database: networking, disk failure, routing, caching. all of that is negated. so yes, there is some latency, but not as much as you think, and honestly, i'd make the trade again in a heartbeat.