You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Back in June, I discovered this repository with a lot of excitement but without doing as much research as I should have. I was drawn to the potential of contributing to an open-source project that had many unmerged contributions. As a beginner eager to get involved and gain experience, I saw this as an opportunity to make a significant contribution by consolidating those changes, making #156 happen.
Over the past few months, I have worked to integrate this library into my project, aiming to achieve clean and efficient map rendering. However, I encountered numerous issues with various functionalities, which turned out to be more challenging than I initially expected. Despite my efforts to resolve these issues and improve the package, deeper and more complex problems have continued to arise, often testing my expertise and schedule.
As an avid user of Deck.GL in a Google Maps-based project, I recently explored the deck.gl-leaflet integration as an alternative. To my surprise, I was able to get it working out of the box with fewer lines of code and significantly more functionality than this package currently offers. This experience has led me to reflect on the sustainability and development activity of this repository compared to the active contributions and support that the visgl organization provides to Deck.GL.
While I still believe in the potential of this library, my dependence on it has diminished. Given the current state of the project and the challenges I’ve faced, I am unable to continue contributing here. I suggest we consider noting Deck.GL as a well-maintained alternative for developers who need to render large datasets with Leaflet.
I understand that this suggestion may conflict with the views of others who value this library and its specific use cases. Please feel free to share your perspectives and feedback. This is my first significant RFC in an open-source project, and I hope it can serve as both a learning opportunity for me and a constructive discussion for the maintainers and the community.
Hello everyone,
Back in June, I discovered this repository with a lot of excitement but without doing as much research as I should have. I was drawn to the potential of contributing to an open-source project that had many unmerged contributions. As a beginner eager to get involved and gain experience, I saw this as an opportunity to make a significant contribution by consolidating those changes, making #156 happen.
Over the past few months, I have worked to integrate this library into my project, aiming to achieve clean and efficient map rendering. However, I encountered numerous issues with various functionalities, which turned out to be more challenging than I initially expected. Despite my efforts to resolve these issues and improve the package, deeper and more complex problems have continued to arise, often testing my expertise and schedule.
As an avid user of Deck.GL in a Google Maps-based project, I recently explored the deck.gl-leaflet integration as an alternative. To my surprise, I was able to get it working out of the box with fewer lines of code and significantly more functionality than this package currently offers. This experience has led me to reflect on the sustainability and development activity of this repository compared to the active contributions and support that the visgl organization provides to Deck.GL.
While I still believe in the potential of this library, my dependence on it has diminished. Given the current state of the project and the challenges I’ve faced, I am unable to continue contributing here. I suggest we consider noting Deck.GL as a well-maintained alternative for developers who need to render large datasets with Leaflet.
I understand that this suggestion may conflict with the views of others who value this library and its specific use cases. Please feel free to share your perspectives and feedback. This is my first significant RFC in an open-source project, and I hope it can serve as both a learning opportunity for me and a constructive discussion for the maintainers and the community.
Ref: visgl/deck.gl#8941
The text was updated successfully, but these errors were encountered: