Another must-watch #reactjsconf talk: “Unlocking the structure of your React applications with the AST” by @gnijorhttps://youtu.be/OZGgVxFxSIs?list=PLb0IAmt7-GS1cbw4qonlQztYV1TAW0sCr …
-
-
Replying to @dan_abramov4 replies 0 retweets 4 likes
-
Replying to @dan_abramov
@dan_abramov@babeljs@sebmck@gnijor you could do so many cool things easily with sweet.js macros1 reply 0 retweets 2 likes -
Replying to @jlongster
@jlongster@babeljs@sebmck@gnijor I usually aim for “no user code” or “as little user code as possible” for instrumentation tools1 reply 0 retweets 0 likes -
Replying to @dan_abramov
@jlongster@babeljs@sebmck@gnijor Can I use Sweet.js like that? As a behind-the-scenes transform tool?1 reply 0 retweets 0 likes -
Replying to @dan_abramov
@dan_abramov@jlongster@babeljs@gnijor No, you need to invent new syntax for sweet.js macros which is very hostile imo4 replies 0 retweets 0 likes -
Replying to @sebmck
@dan_abramov@jlongster@gnijor the types of transforms you can do is also quite basic. Doesn't really lend itself to complex stuff.1 reply 0 retweets 0 likes -
Replying to @sebmck
@sebmck@dan_abramov@gnijor this is completely wrong... advanced systems like Racket (which sweet is based on) can even do type inference6 replies 0 retweets 0 likes
@jlongster @dan_abramov @gnijor With sweet.js you'd have to input every single grammar production that functions appear in.
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 