SebastianVerified account

@jlongster @babeljs @sebmck @gnijor I usually aim for “no user code” or “as little user code as possible” for instrumentation tools

@jlongster @babeljs @sebmck @gnijor Can I use Sweet.js like that? As a behind-the-scenes transform tool?

@dan_abramov @jlongster @babeljs @gnijor No, you need to invent new syntax for sweet.js macros which is very hostile imo

@dan_abramov @jlongster @gnijor the types of transforms you can do is also quite basic. Doesn't really lend itself to complex stuff.

@sebmck @dan_abramov @gnijor this is completely wrong... advanced systems like Racket (which sweet is based on) can even do type inference

@jlongster @dan_abramov @gnijor With macros it's extremely brittle and if you venture even slightly from what the macro describes it fails.

@jlongster @dan_abramov @gnijor Also you have no access to scope tracking etc. Extremely limited in what you can do.

@sebmck @dan_abramov @gnijor (last min correction: you can have access to scope :))