5 reasons to use Leaflet JS | Introduction to Mapping Libraries

Hey everyone! New series I'm starting up doing quick overall reviews on top mapping libraries. We're starting off with LeafletJS!
leafletjs.com/
00:00 Introduction
01:15 Open Source!
02:30 Great for new ideas
03:50 Easy for developers
04:55 A great community
06:00 Awesome plugins

[@JaRatr]

My favorite part about leaflet is following their quick start guide step-for-step and viewing the gray box it produces. Fun stuff...

[@johnsnow8252]

Totally agree with you. Leaflet is great, simple but powerful, sutiable for building prototype. But I prefer mapbox-gl-js for production😂.

[@kirkislas4320]

thx for putting me on bruh

[@mabrarrubaiyatislam5653]

So, Which library should I use for heavy data. consider 60 thousand rows of line geometry and 1,80,000 rows of point geometry I need to pull hit and convert to geojson to show in map. it is becomes quite slow.

[@learnwithmapster]

I'd be loading that in as part of a base tileset via something like Mapbox and MTS

[@denischikita]

Confusion brings what concept of tiles and controller lib separation. So I just don't agree what leaflet is simple. I found it pretty confusing even on basic tasks. For example I can't customise geocoding input and i cant use my own as source to geocode API, at least there is no clear documentation on it. So I end up with Google Maps, because they have all in one package and fine documented manual.

[@learnwithmapster]

I would say that Leaflet and Google maps have a similar overall philosophy when it comes to the way the libraries function (compared to Mapbox/Maplibre, for instance). However, Leaflet does have plenty of complexity when it comes to integrating functionalities that aren't core to leaflet, like geocoding, as you mention -- you'd need to use external plugins. Glad you found your solution in Google Maps -- although were you able to plug in your own geocoder there?