4 ms·
You think they wanted to own more of their product, integrated OSM, and now if there's complaints or things to change they're like "sorry nah"? That doesn't so
by refulgentis 3y ago
You think they wanted to own more of their product, integrated OSM, and now if there's complaints or things to change they're like "sorry nah"?
That doesn't sound right to me, I'm curious if you have any examples or sources
- reaperman 3y agoI think GP is saying they expect Lyft respond to complaints or things to change by fixing them in their internal OSM database, but maybe not propagate those changes back to canonical OSM for everyone else to enjoy.
- Ajedi32 3y agoCouldn't that become hard to maintain after a while though, once the OSM map changes and they start getting conflicts? I think that's often the biggest reason why corps contribute back to open source projects rather than maintaining internal forks for everything. I guess it's possible though they could just deal with that if they feel like having better maps is a significant competitive advantage, but if the goal is just to not be dependent on Google upstreaming the edits sounds like a better idea.