Thanks! * The output is pretty robust. Everything compiles down to just a few basic forms: an atom, a function, lambda, and "if". I'm considering adding a form

Thanks! * The output is pretty robust. Everything compiles down to just a few basic forms: an atom, a function, lambda, and "if". I'm considering adding a form that lets you output raw JS if you need to optimize something, but I have yet to see the need for that. * Outlet doesn't do anything crazy like CPS. When you call a function "foo" with "(foo 1 2 3)" it generators a simple function call "foo(1, 2, 3)". So you can call native javascript functions normally. You can use arrays and objects inline, like so: (define a [1 2 3 4]) (define b {:key "value" :another-key "value2"}) Those get generated to normal javascript arrays and objects, so you can pass them as parameters to a native js function if needed. You can even reference objects with "." like: (define foo {:one 1 :two 2}) (print foo.one) That works as expected. The only difference is vector reference, instead of "foo[1]" you would do "(vector-ref foo 1)". Of course, this is all subject to change, but the goal of Outlet is to not do something crazy and for things to work as expected.