Sebastian

@chicoxyzzy No idea how or why people use it. But Flow should accept and run all Babel ES5 output without a problem and if it doesn't then it'd be a...

@backspaces Some parts of that article are outright wrong. Such as coffeescript `->` being equivalent to ES6 `=>`. The performance of 6to5 is definently concerning and i'm hoping to make...

Biggest benefit to ESTree is interoperability which Shift does not have (I know an AST converter exists but it's not really the same thing). Is any outside of Shape using...

Just so we're clear, you consider month long discussions like #32, "moving too fast"?

I think you're thinking too much into it. It's an AST spec, it's relatively straight forward, no "baking process" required. If node types can't be agreed upon in a timely...

I don't understand your requirement for versioning. What's the point? (As it's been said, backwards compatibility is not going to be broken) What if a parser only supports certain parts...

@michaelficarra > Finally, are we sure we want to have this discussion here? It seems a bit out of scope for this project. Completely agreed. We haven't even agreed on...

@michaelficarra The SpiderMonkey AST isn't going away (in fact some people such as me prefer it). Try not to let your bias interfere too much with the projects direction.

@mikesherov Sure I don't see why not. Would make it much easier for linters and for transformers that want to retain input whitespace etc.

@millermedeiros > My next step is try to convince that keeping the same structure as the AST is not a good idea. If that doesn't work I'll let you guys...