> That's true. But that's up to the company deciding over the operating system and the browser in the end. The OS is far more powerful, and allows for deeper i

> That's true. But that's up to the company deciding over the operating system and the browser in the end. The OS is far more powerful, and allows for deeper integration and writing in far faster languages. The browser abstracts away the machine. Most JS writers today have no idea or understanding of the actual computer they are writing against. It's a sandbox for them, and it's the reason apps today bloat to hundreds of megabytes and burn CPU to do the most mundane thing. Less distance from the metal is better in my book. > Native in this case means running on one platform. I would much rather focus on making something that works for a bigger part of the world. Feels like a strawman / bad faith argument. As a user, I'd rather use one fast app on my device, I don't care if some guy on another platform can use this product. As an engineer, I want happy users, and if that means writing X clients, so be it.