seems they just used mapbox defaults. if your device can't run mapbox something is wrong with your device, it's a common and well supported library.

Example 3D globe maps on Mapbox website run very smoothly, so it’s not that.

Take a perfectly smooth animation, add a fast-looking synchronous function call in the animation loop, get some jank. A modern GPU, even integrated into a CPU as usual on laptops, is ridiculously fast for the task of showing a globe, something like 100k triangles at worst. But you need to feed it on time.

Maybe also browser dependent? Constantly janky on Firefox/Windows/8840HS laptop; janky on Chrome while loading new locations but then mostly very smooth.

FYI I'm on a 2015 MBP and Firefox is doing ok here, so I suspect this is a perf problem with Safari.

The service seems to believe there are multiple charging sites in the middle of the North Sea - which seems slightly unlikely...

57.782509, 2.295993 should have been 12.295993. For those "Data Provider = NOBIL", but good to see there is an edit and comment feature.

I'm actually slight disappointed that there isn't some bizarre explanation for why North Sea rigs have charging points - preparing for electric helicopters maybe? ;-)

Driving my electric car to my oil drilling job in the middle of the ocean, as I do every day

The guy running the project doesn't seem to have the time needed to improve the site:

https://github.com/openchargemap/ocm-app/issues/37