Hacker Newsnew | past | comments | ask | show | jobs | submit | ivansanchez's commentslogin

You work for Mapbox, a US-based company with offices around the world.

Do you still perform your day-to-day work? How's the relationship with your colleagues these days? I'm curious about the people in Belarus in particular.


No, Mapbox has been very supportive, trying to help however they can and obviously not expecting me (or anyone else in Ukraine) to work any time soon.

Same for colleagues from Belarus and even Russia — they are strongly pro-Ukraine and anti-war, although stating this publicly can easily get them in jail (already happened multiple times).


are they still paying you?


Yes. Although I’m intentionally delaying invoices so that I have unrealized funds outside of the country, just in case.


I'll have your back regardless, let me know and if you and/or your wife and kids need to come to the West I'll be more than happy to pay your way/assist in any way that is required. Mail me: jacques@modularcompany.com Hang in there and stay safe, all of you. Scary times!


Indeed! From my point of view, WebGL rendering for Leaflet makes sense, but it's very important to not remove support for browsers which don't implement WebGL right now.

MapboxGL is very performant, but it changes all the abstractions to the map elements, which is something I'm particularly not very happy with. Thus Leaflet.GL.


Leaflet maintainer here. AFAIK, Leaflet still has a nicer learning curve compared to OpenLayers (which doesn't affect long-term OL users like you, obviously), and a plugin ecosystem which allows for smaller library size.

The OL3 folks have been working hard on making OL3 leaner (see the "Faster, smaller, better" talk from FOSS4G Bonn here: http://video.foss4g.org/foss4g2016/videos/index.html), but I feel Leaflet still has an edge on that regard.

Also, OL3 depended on the Closure compiler for a long time, which made it difficult to interoperate with other frameworks, which is why a lot of React/Ractive/R/Django/Vue users choose Leaflet.

Other than that, there's no clear obvious advantage of a library over the other one. We have a friendly relationship with the OL3 folks, we try to copy some of their features, they try to copy some of ours, everything gets better in the end.


No, you don't lose access. You just have to work around some nuisances. Have a look at https://gitlab.com/IvanSanchez/Leaflet.GridLayer.GoogleMutan...


some nuisances? like having to load and use the google maps api.

I'm interested to know if this doesn't actually violate the google maps terms of service:

https://developers.google.com/maps/terms#10-license-restrict...

10.4(e): No use of Content with a non-Google map. You must not use the Content in a Maps API Implementation that contains a non-Google map.


That Terms contains some interesting junk.. for example is a webpage considered "software"?

10.5(f): No incorporating Google software into other software. You will not incorporate any software provided as part of the Service into other software.


Yeah, at that point I wouldn't be comfortable touching it.


Leaflet maintainer here. There is some work on a rotation code branch, plus I've been working on something called "Leaflet.GL" to do WebGL rendering. The OL3 folks just have more time and resources, you know. Also Leaflet must still work with IE8 (OL3 doesn't, there are some cases where that's needed).

We have a friendly relationship with the OL3 folks, even though sometimes we're jealous of their WebGL rendering, and sometimes they're jealous of our lower learning curve.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: