Discussion: open source future of react-native-mapbox-gl #1124
Replies: 4 comments
-
@gmaclennan we have minimal resources. So i don't think maitaining a fork of mapbox-gl-native would be in reach for us. (Also i'd like to note that AFAIK opensource mapbox libs uses OpenGL, that is deprecated on iOS platform, and probably a very much non trivial change to make it use Metal) With 8.1.0 we default to old (open source) mapbox libs. And you can use Pod/gradle to use the latest non opensource mapbox libs. I agree that it's very sad that mapbox is no longer opensource, but i think this lib will support the latest (non-opensource) mapbox libs in the longerterm |
Beta Was this translation helpful? Give feedback.
-
Thanks @mfazekas, that is clear and makes sense. |
Beta Was this translation helpful? Give feedback.
-
I have started a discussion about a solution for this problem: https://github.com/react-native-mapbox-gl/maps/discussions/1274 |
Beta Was this translation helpful? Give feedback.
-
Cross posting this here: |
Beta Was this translation helpful? Give feedback.
-
I had not noticed until the mapbox-gl-js v2 announcement that
mapbox-gl-native
is no longer being maintained in the open, and from[email protected]
and[email protected]
those SDKs use the closed-source binary of mapbox-gl-native, and require a Mapbox token to use.We use this library in our open-source app for indigenous mapping and monitoring, Mapeo and are committed to open-source tools wherever possible. I am wondering what thoughts others have about ongoing support for native maps code? A community maintained fork of
mapbox-gl-native
is a possibility. The Android and iOS SDKs remain open source, but I would assume the rely on internal details of themapbox-gl-native
library, so I am not sure what it would take to also maintain those. New features are not critical for us, but bug fixes are important.I guess one possibility for the future of this library is that it uses the Mapbox-licensed SDK / native library, I guess in a similar way to what
react-native-maps
does with the Google SDK. I'm interested to know which direction the maintainers here are thinking of taking, and what others that use this library are considering for options for an open source native mobile mapping library.Beta Was this translation helpful? Give feedback.
All reactions