Live data from Hacker News

Mapbox-gl-js is no longer under the 3-Clause BSD license

github.com

91–100 of 200 posts

Re: Mapbox-gl-js is no longer under the 3-Clause BSD license

#91

It's understandable. People tend to forget the obvious, that the primary goal of Mapbox is to make money. Investors have given their money to Mapbox with the expectation that they will get back more, preferably much more.

I have nothing against people wanting to make money but don't put a free product then yank it out under my feet once I'm comfortable using it (I'm not affected in this case since i don't use mapbox, but the CentOS treachery is still hurting).

At least 50% of my work projects happen because the resources I'm using are free. If it isn't free, the project either doesn't happen, or I spend a few months coding what is missing.

So I'd rather they tell me upfront that I can't afford their product than waste my time.

Re: Mapbox-gl-js is no longer under the 3-Clause BSD license

#92

Earlier quoted context omitted.

Can you point to where/when this happened for their native code? As far as I can tell, that's still licensed under 2-clause BSD ( https://github.com/mapbox/mapbox-gl-native/blob/master/LICEN... )

Everything in that repo is 7+ months old. The main GL renderer is now closed-source: see https://github.com/mapbox/mapbox-gl-native-android/pull/450 .

thanks!

Re: Mapbox-gl-js is no longer under the 3-Clause BSD license

#93

It's understandable. People tend to forget the obvious, that the primary goal of Mapbox is to make money. Investors have given their money to Mapbox with the expectation that they will get back more, preferably much more.

There are many companies making money with open source. Mapbox used to make money by providing APIs - apparently it didn't work out.

Re: Mapbox-gl-js is no longer under the 3-Clause BSD license

#94
post #57

"Mapbox proudly embraces our open source roots" http://www.mapbox.com.s3-website-us-east-1.amazonaws.com/abo...

I wrote that paragraph and I agree with the decision to change GL JS's licensing.

I'd be interested to hear why. I have no problem with companies choosing not to open source in the first place, it is just the idea of taking an open source project with an active community around it and closing it up that is a tough pill to swallow.

Re: Mapbox-gl-js is no longer under the 3-Clause BSD license

#95
post #32

Earlier quoted context omitted.

That doesn't answer the question. And has nothing to do with closed source, really.

yeah, posted notes/deets https://www.mapbox.com/blog/mapbox-gl-js-v2-3d-maps-camera-a... Developers need a Mapbox account and access token. v2 is available in the same way as v1 -- the project source code is available on Github at https://www.mapbox.com/blog/mapbox-gl-js-v2-3d-maps-camera-a... for open collaboration with the community. New features will be on v2.

Please stop the open-washing: v1 was available under the BSD open source license, v2 is not. You are making a fool of your company by acting as if open source is not important.

Re: Mapbox-gl-js is no longer under the 3-Clause BSD license

#96

It's understandable. People tend to forget the obvious, that the primary goal of Mapbox is to make money. Investors have given their money to Mapbox with the expectation that they will get back more, preferably much more.

I have nothing against people wanting to make money but don't put a free product then yank it out under my feet once I'm comfortable using it (I'm not affected in this case since i don't use mapbox, but the CentOS treachery is still hurting). At least 50% of my work projects happen because the resources I'm using are free. If it isn't free, the project either doesn't happen, or I spend a few months coding what is mis…

> but don't put a free product then yank it out under my feet once I'm comfortable using it

Why? This strategy often maximizes shareholder value. Provide a free product in the growth phase and once you shake off competitors and build a moat (aka a monopoly), you start taking profits. Charging money during the growth phase will slow down the growth.

Re: Mapbox-gl-js is no longer under the 3-Clause BSD license

#97

Well, that sucks. I've been a happy Mapbox GL JS user for years, hosting my own tiles and not using their service at all. I even had a few (very small) pull requests accepted into the project. Hopefully the OSS community can maintain a fork of the 1.x codebase. -edit- The FAQ says developers can still use self hosted tiles, but also says that usage is now billed per map load, and "a map load occurs whenever a Map obj…

Can't you just use the old version? Only the new code is under this new license.

Re: Mapbox-gl-js is no longer under the 3-Clause BSD license

#98

Earlier quoted context omitted.

yeah, posted notes/deets https://www.mapbox.com/blog/mapbox-gl-js-v2-3d-maps-camera-a... Developers need a Mapbox account and access token. v2 is available in the same way as v1 -- the project source code is available on Github at https://www.mapbox.com/blog/mapbox-gl-js-v2-3d-maps-camera-a... for open collaboration with the community. New features will be on v2.

Why would the community want to collaborate on a project that's not openly-licensed?

There might be a bug that only affects a handful of people and doesn't get prioritized by the company. Then one of those people might want to collaborate on the project just to get their personal pain point fixed.

Re: Mapbox-gl-js is no longer under the 3-Clause BSD license

#99

Earlier quoted context omitted.

Founder, Stadia Maps here. We're looking into this, as well as trying to build consensus with the other map vendors on how to approach it. If you're a vendor and what to be part of it, email me (luke at stadiamaps.com).

Doesn’t deck.gl also use map box? What are they doing?

deck.gl uses mapbox-gl for the basemaps, but it can run without mapbox-gl.

You can use deck.gl + Google Maps: https://deck.gl/docs/get-started/using-with-map#using-deckgl...

Deck.gl has also a MVTLayer: https://deck.gl/docs/api-reference/geo-layers/mvt-layer

Re: Mapbox-gl-js is no longer under the 3-Clause BSD license

#100
post #76

Earlier quoted context omitted.

afaik, Mapbox's geocoding service was never meant to provide the lng,lat of retail entities. Looking over their API docs, you can search for points of interest (POI), but that's it: https://docs.mapbox.com/api/search/geocoding/ For your use case, you should look into a geocoding service [0]. And then you can display the location results with your mapping library of choice. Google Maps does provide an all-inclusive se…

> The Mapbox Geocoding API does two things: forward geocoding and reverse geocoding. Forward geocoding converts location text into geographic coordinates, turning 2 Lincoln Memorial Circle NW into -77.050,38.889. https://www.mapbox.com/place-search I think "location text" is the part they are not parsing well. The screenshots all over that page show someone entering a couple of letters and getting the resulting POI w…

Their geocoding seems to work decently enough for street addresses from what I've seen, which is what it's technically advertised to do. It doesn't have a Google-sized database of business entities, so I'm not surprised it doesn't work for any POI less significant than a major landmark (i.e. "city hall", "the statue of liberty", etc.)

Pretty common to use Google to look up an entity (to either get address or full geocoding results) and then Mapbox to do the display though.

Post reply on HN