sudowork

Thanks for the tip! Given some of the lessons we've learned with CoffeeScript, we'll most likely wait until proposals hit at minimum stage 3 before adopting them.

When we performed our conversion, decaffeinate@2 did support ES2015 import/export - it was actually the default which could be disabled using (`--keep-commonjs`).

With decaffeinate@3, you can convert using ES2015 module syntax with the `--use-js-modules` flag.

Although we don't plan on using CoffeeScript for the reasons outlined in the article, I do want to mention CoffeeScript 2 does aim to target ES.next features and offer interoperability. Specifically, CoffeeScript 2 does support async/await http://coffeescript.org/v2/#async-functions.

No problem! Hope it comes in handy :).

I agree, it's one of the features we'll miss.

There is a Stage 1 Null Propagation proposal: https://github.com/tc39/proposal-optional-chaining

Thanks for the fast response! I'm really hopeful for the future of Light Table, and I appreciate the work you've put it.

Small bug I found: When I change the editor theme to something other than `default`, the next time I start up the editor, the theme isn't loaded. Instead, I just get some light grey text on a dark grey background.

UX Annoyance: When clicking on an exception, there's no visual indication that it's been clicked on. I found that Shift+Tabbing brings you back to the editor pane (other than using the mouse).

A couple more things that could just be me being stupid. When I try to eval using Ctrl+Shift+Enter, nothing happens. Instead, I have to eval each line one-by-one. I tried creating a new key binding, but couldn't figure out how to delimit my keys to allow modifiers. I also can't figure out how to pop up documentation or data flow as demo'd in the original light table (this is my first time using any version of light table). I tried `(doc <foo>)`, but it just evaluates to `nil`.

Anyways, hope these comments might be useful in terms of my user experience as a first time user.

Unfortunately, for our team, we had to revert to a version of our generator that was about 5 hours old due to a issue with one of the library dependencies. We didn't catch this until last minute, so basically all of our low-level pixel analysis got thrown out the window.