JavaScript boy and “lovely thoughtleader” 
he/him 
You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
Beware JSX!
Even worse... In Flow/TS there's already ambiguity with JSX and arrow functions with type parameters. const jsx = <X>() => {}</X>; const arrow = <X>() => {};
Don't point tags require / before >? (<X/> in the second line)?
Second line is an arrow function with a type parameter. As a regular function: function foo<bar>() {}
What if we just make JS parsing rules stricter if you want to use JSX and Flow/Typescript. Like requiring spaces around operators. I know we call them supersets of javascript, but maybe they don’t need to be strict supersets.
That's not really necessary. Ambiguous syntax doesn't mean spec incompatible. Type arguments on calls are the only syntax extensions that cause otherwise valid regular JS to be parsed differently.
the first one would be a syntax error. The curly brackets can’t be empty the rest would treated as the string child of JSX.
I'm not sure what you're saying. Both lines are valid syntax in TypeScript and Flow. The first line is a JSX element with the string contents "() => {}". The second is an empty arrow function with an X type parameter. https://astexplorer.net/#/gist/b7ec982c0246be182a05ed0c7dbc3dd0/873d02db09fbe182d655663cbeff8d3c3b161244 …
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
