Just chiming in as a software engineer. My product DOES support Firefox, but there are some weird animation quirks that my team has been trying to solve, but with limited bandwidth and a full product backlog, it’s hard to justify spending too much time supporting a browser with such small global utilization. Especially since we’re using third party libraries like angular material, quirks on smaller browsers can be a nightmare to chase down

That’s early adopter pain for you. In Europe there is one standard, and in the US, we’re getting there. Yes it’ll be a pain for a while that people with CCS ports will need to use adapters at NACS chargers and vice versa, but we’re settling on the underlying CCS technology being the standard, so it’ll just be a matter of connector. Much better than the three standards we had very recently (add chademo)