You might get some pushback on this line:

"and informal benchmarks in the Chrome console would indicate that creating a blank object and then setting properties on it costs about the same as creating a literal object with the same properties"

Some folks might try to split hairs with you on that.

yeah, I would be interested in seeing if other people get different results. What I was seeing was so similar that I wondered if both forms were being handled the same way by v8.

One thing you could maybe do is introduce the reader to the general issues and confusion that surrounds name munging and advanced compile. js-interop is really helping us out in making that all easier to deal with, but novices probably don't even have a solid understanding of what the problem is and why js keys do one thing sometimes and another thing other times.

that is a good idea. am thinking that might need its own post.

But that' may be too verbose of a tangent. The follow-along-with-code-examples is working well.

right

may be able to show examples directly, via the closure compiler api service

Just finished. Really good!

thanks for reading! and for the ideas.

Thanks for js-interop! 🙂

i am doing some simple tests on https://closure-compiler.appspot.com and finding that even in simple mode, closure re-writes the “create blank object +then add properties” into literals

I was wondering if that was happening

the tests I did in Chrome / http://jsperf.com didn’t go through the closure compiler, but it wouldn’t be surprising if v8 does essentially the same

Thank you @mfikes! I have been watching you and your friends on Apropos Clojure on youtube. Great stuff!

Ahh. Thanks!

I don’t mean to pester you… but I also do have a related doc change to the one I made the other day… https://github.com/clojure/clojurescript-site/pull/313

🙂