Ask HN: Are browsers more likely to adopt .js or .tsx to represent typed JSX?
Node recently allowed importing .ts files. But the types-proposal is adding them into plain .js files. And there's JSX which isn't going away and will eventually be standardized. (My proposal is that we create a self.JSX object with create() factory that you can override at your app's entry point.) Do you think browsers are more likely to add support for .ts/.tsx/.jsx extensions, or allow .js to include types/jsx? (Or both?)
I’ve already seen browsers using inline ts, not too sure about tsx because isn’t that usually compiled anyways? To have the browser interpret that would be interesting, I know some browsers like to onboard more complexity but it seems like it may have some unforseen challenges with conventions like react router