In professional contexts as a software developer you will manage just fine with just English. Free time context and true integration to society will require learning Finnish. But you can take your time with that.
Curious what ”The cycle removal algorithm only uses the reference counts and the object content” means in practice. Is it based on some well known algorithm?
It's a form of protest. If both flatMap and smooshMap are seen as equally "breaking the web", maybe TC39 will coose the less insane name for the method.
Currently there is nothing to stop mappers using tags in wrong ways. It should just be flat out impossible. If a field/tag isn't defined in the schema, it could not be used. The range of values should be limited in the same way, too.
Im my opinion the biggest problem is the data model (or lack of). Tags i.e. key-value pairs are used to add properties to geometry. Mappers use different combinations of keys/values to describe the same thing. The post touches on this, but does not offer solutions other than adding "layers".
There should be a strict schema that would be community managed through some process.
WASM code can call external functions defined per module, and the external code can be JS code that interacts with browser APIs. So indirect use of browser APIs is possible.
WASM isn't related to JavaScript in any way. Maybe you were thinking of asm.js?
You cannot access the browser APIs from WASM so there is no tight coupling with the browser environment. I think non-browser use could make definately sense.