The greatest trick the devil ever pulled was convincing the world that the .js extension could have non-standard syntax
-
-
This Tweet is unavailable.
-
Nope, FB idioms all use .js for that syntax
End of conversation
-
-
-
And .TS too

-
They have their own dedicated and managed extension, which is a much better solution and isn’t reusing .js like my original tweet describes
End of conversation
New conversation -
-
-
Tagged template literals would have been a way this could have been mitigated. I guess that may have felt not as cool.
-
JSX: Maybe, but not: https://github.com/facebook/jsx#why-not-template-literals … Flow: How would that work?
- 1 more reply
New conversation -
-
-
*eyes CommonJS*
- 1 more reply
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
he/him 