marisen

There's another path that the author hasn't considered, which is making users contribute directly to OSM.

To contribute a bookcase, ask them to create an OSM account, log in with OAuth, and send the edit straight to OSM.

Book corners becomes just a custom view and editor over OSM data, instead of being its own database.

Users are now responsible for the data they submit (OSM already has tools to deal with vandalism etc...).

WhatsApp doesn't use libsignal, and Android is already pretty Rusty and deployed more than WhatsApp around the world (not just smartphone. Tons of "embedded" use cases also run on custom Android)

It is well known that a programmer that stops programming stops requiring food

> React, the defacto UI framework for Javascript has a lot of web assembly components.

I'm pretty sure this is just plain false. Do you have an exemple?

If you use a lot of Arc<Mutex<Box<T>>> you you probably just learn to use Rust properly and just use Arc<Mutex<T>> instead because it pretty much never makes sense to have a Box inside an Arc...

I say that as someone that thinks Rust's learning curve is the main reason it rarely makes economic sense to use it.

It's a french project funded in part by the french government and the only current instances are for french contributors. They actually make it pretty easy to contribute... for the people that will contribute in France.

There are currently only 2 panoramax instances. One from IGN (french "National Geographic Institute) and one from the french OSM charter.

This is obvious by looking at the coverage the world. France it where the majority of the coverage is. The coverage of most cities is actually pretty impressive for a young project.

While the UI and coverage is not necessarily on par with street view, it's still pretty usable in France.

Secondly Panoramax is first built for OSM contributors/mappers, not for end users. The blog reflects this in the tldr: "If you are interested in contributing"