Most desktops, even those with crappy Intel GPUs have superior GPU performance to the best mobile devices. WebGL has poor penetration, but you really don't take much performance hit as long as you don't need to process data in JS, but then again, a modern i5 or i7 is much faster than an ARM on a mobile device, so what you loose in JS performance, you gain in CPU performance.
Current JS and WebGL performance is well within the range needed to make this work. MapsGL is already rendering a quite large workload, in fact, my intuition is that the 2D rendering, especially with rasterizing label text all over the place, is likely more expensive than navigating an octree and rendering a mesh.
Current JS and WebGL performance is well within the range needed to make this work. MapsGL is already rendering a quite large workload, in fact, my intuition is that the 2D rendering, especially with rasterizing label text all over the place, is likely more expensive than navigating an octree and rendering a mesh.