Greg Tatum

Coming in to say I'm actively getting issues because d3's latest version is only using ES6 syntax. I can't use my browserify tooling now. The time seems ripe for this...

Hmm... Yeah my bad. It looks like user error on my part. Sorry about that. My opinion still stands though. Three.js just landed a big patch to go the ES6...

Thanks @jmm and @terinjokes! I think that is very well reasoned, and I agree with where you all are coming from. I'll probably end up adding another tool to help...

For anyone coming into this thread, the browserify transform [rollupify](https://www.npmjs.com/package/rollupify) will take all of your ES6 import statements and hoist them all into a single module scope.

No worries, it worked like a charm once I figured it out! Thanks for publishing this module, it's really handy: http://sessions.gregtatum.com/013/

From a web compatibility perspective, it would be bad if a product had a really good spell checker implementation when backed by V8 due to custom `Intl.Segmenter` changes, but then...

The render function for the context menu will need to detect what TYPE of track was clicked, then add this option to hide all of the tracks by that type:...

For what it's worth, removing the track ordering feature would most likely fix this issue.

Also, we have the `uintArrayToString` which we can use for better compression of the arrays of indexes. We are already using this for CallNodePaths.

This is a single batched message update: Notice the ObjectInspector dominating the timing.