Speaker 2
And then what will happen is someone else in the community will build a gem or does something that's very awesome, and a lot of people will start using it. And then what will end up happening is internally, like on the rails, you know, it's open source te open source team. Well, then say, hey, this is interesting. We should pull this into ruby, ruby on rails. And that's happened a number of times. Ik, we're going to base er, going to pull it in, or e're gongto recreate it, because it's something that's actually needed in the framework. And so i'm wondering is maybe this is a issue further up that needs to be addressed, like as it's something at google level, where, hey, maybe google needs to open up a little bit more for andrewitsa. Hey, here's, you know, there's this m p android chart, like, it works straight. What isn'tt like, you know, they did that with dagger, kind of, they kind of pulled that end. And i'm not going to defend dagger, but it's utu.
Speaker 1
But, you see, that's, like, your proving my point. Thet did tatit dagger, which is r fancy injection framework. You know, how often do you find that for like, no, yes,
Speaker 2
exactly. I mean, that solves tat problem. But, like, it's ke charting like that would be very useful. You know, what are some of theri'm trying to think off the top of my head, some of the other platform apas it would be really nice to have. It's
Speaker 1
just like, the biggest painful things, if you think about a relic. I know for a fact, shon f navigation is still a pain in the butt. Lucky. I know there's ap navigation, and it's better. And, you know, i actually do use it in one of our aps here. It's still not very indutive, though. I canow. It's still not like, just, aha, i can use this, and now my ap navigates between screens in an easy, fluid way. I don't think that's true, right? What other examples? The charting appears like a good, obvious example, especially because it came from recent memory made.
