kosmtik VS iD

In that case, openstreetmap.org uses the Carto style by default, for which Kosmtik should do the job, but I haven't personally tried it to know how to use it. JTileDownloader also might work to download the tiles directly from the website, but again, haven't used personally.

It's a known issue with the iD editor: https://github.com/openstreetmap/iD/issues/7381

For me a good example have always been https://kangax.github.io/compat-table/es6/ which rendered very poorly on Firefox. I see it's better now, but still, try to hover over the table (do couple of mouse movement, some circles or something) and see that it's not as responsive as Chrome is.

Another example is iD[0] Editor on https://www.openstreetmap.org/. But there, to be fair, it's also slow on Chrome but I feel it's a bit slower on Firefox.

[0] https://github.com/openstreetmap/iD

I've had limited success in getting some imagery in Josm, using the rather old Streetside plugin. Some of the problems may be in one of the libraries used to access the Streetside API, but there are also issues with standard Bing aerial imagery in editors too.

website AND contact:website are not supported by iD, so further updating the POI with iD won’t expose the values properly: https://github.com/openstreetmap/iD/issues/5015

FWIW: https://github.com/openstreetmap/iD/issues/7199 is where this issue is being tracked.

I hope my first reply didn't sound too brusque. It's not just you - it seems like it's a known problem for iD in the UK and not (yet?) solved. https://github.com/openstreetmap/iD/issues/9153

The day iD adds a simple way to measure width on aerial, it will get mapped everywhere. I exaggerate, but OSM is a work in progress and better tools means better maps. Hell, RapID can probably eventually offer values automatically. If only JOSM didn't look like accounting software, people would micromap there more too.

Created an issue here :) https://github.com/openstreetmap/iD/issues/8900

I think, indoor mapping support is indeed something to consider. It is a rather advanced mapping concept, so it might not be on the top of the todo list right now. However, I'm seeing that some work on this was already done (see https://github.com/openstreetmap/iD/issues/4780 / https://github.com/openstreetmap/iD/pull/3097), so it might be actually a relatively quick thing once the outstanding UI questions and issues are resolved.