- GeoJSON-VT (fast GeoJSON processing) https://github.com/mapbox/geojson-vt
- Earcut (triangulating polygons) https://github.com/mapbox/earcut
- Supercluster (point clustering) https://github.com/mapbox/supercluster
- vt-pbf (converting GeoJSON tiles to VT) https://github.com/mapbox/vt-pbf
- vector-tile (decoding vector tiles) https://github.com/mapbox/vector-tile-js
- pbf (fast reading/writing of protobuf) https://github.com/mapbox/pbf
- TinySDF (generating SDF from local CJK fonts) https://github.com/mapbox/tiny-sdf
- Potpack (generating sprite layouts) https://github.com/mapbox/potpack
- grid-index (spatial index for collisions/querying) https://github.com/mapbox/grid-index
- Pixelmatch (image comparison in render tests) https://github.com/mapbox/pixelmatch
- Polylabel (fitting labels into polygons) https://github.com/mapbox/polylabel
As far as I know as someone who worked here for 7+ years (take this as personal opinion), Mapbox wants to keep investing heavily in open source and open data sustainably and indefinitely, and this GL JS change is an unevitable prerequisite for that. This may not be easily apparent at this moment but it will be soon.
Introducing a drastic billing change under the implied threat that your year or more of man hours performed using an underlying open source library with an understandable billing model is now potentially at risk, is shady. These billing changes make some self hosted tile users go from $0 to tens of thousands of dollars a month in usage. It’s shady, don’t lie to yourself.
Also, you are not your company. I am not saying you are shady, because you are just a person who has bills and a skill and you need a salary. Don’t conflate criticisms of your employer as attacks on yourself, or you can have a hard time seeing what other people see. Tricking yourself to believe something that might not be true is one of the worst thing you can do.
This only happens if the developer deliberately upgrades and adds a token. If you do nothing and you keep using v1 - nothing changes for you.
The frustrating thing is that we just went through this with google. We paid a reasonable amount, but then got extorted to pay more or jump ship. We jumped ship to a reputable company, mapbox, and we paid a reasonable sum of money for how we used the software, and now the cycle continues. To be clear, I am not complaining that we are paying $0 and we should get the benefits for free. I am saying that we shouldn't be jumped up multiple orders of magnitude in cost, which isn't in-line with our actual usage. That's the shady part.
With move like this, what's the difference?
(Yes, I do share anonfornoreason's sentinent in the sibling comment.)
It's no different to the likes of Oracle. Oracle also employs hundreds of people.
But hey, if you think everyone who criticizes it is full of vitriol, I don't think any further discussion is needed.
In Mapbox there was an easy way to build mapping tools. It let you create rubberbands, hook into map events. Is that possible with Tangram?
* A single style specification format that works well for both base map rendering and data overlays
* Parity across native and web rendering
* Smooth SDF text rendering with decent i18n support
* A font to SDF renderer that is open source: https://github.com/mapbox/node-fontnik
* A tiled data format that is open source: https://github.com/mapbox/vector-tile-spec
I hope this licensing change can spur some competition among open source renderers. I’d recommend taking a look at:
* Tangram: https://github.com/tangrams/tangram - another WebGL based renderer with some key advantages over MapboxGL JS such as custom shaders and canvas text
* OpenLayers: https://openlayers.org has some vector and WebGL capabilities now as well
* Harp: https://www.harp.gl is another new WebGL option
I've been working recently with Tangram, so contact me (see user link) if you have questions or are interested in collaborating!