[Question] How does babili compare to Babel + UgligyJS w/ ES2015?

It appears, all the benchmarks listed aren't run on ES2015 code.

Imagine NodeJS or a modern browser as a target for code that contains classes, rests, spreads, etc - how does code optimized with babili compare (at runtime) to code that has run through babel + uglify?

I've been having transform issues with my codebase; some babel plugins I'm using don't play nice with babili (and cause incorrect dead code removal or undefined references) and using babili CLI isn't going to happen any time soon; over 6MB of JS keeps throwing a FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - JavaScript heap out of memory.

Review the existing benchmark material and the babili CLI context described in the issue, then compare the stated ES2015 scenarios with Babel plus UglifyJS. The issue names no files or tests; done would require an agreed comparison result and a reproducible resolution for the reported transform, dead-code-removal, or memory problems.

Written by the indexing model from the issue text.