| description |
<p><a href="http://keminglabs.com/">Kevin Lynagh</a> will talk to us about data-driven web applications with ClojureScript:</p>
<p><span>A web page or application is, at its core, just a visual representation of data that people can read, look at, and manipulate.</span> <span>Typically the mapping between the abstract data and elements on the screen is implicit in the code: take some piece of the data, do X here, do Y there; when the user clicks on that thing, modify the page here, and so on.</span></p>
<p><span>Reasoning about such code is difficult: either control is inverted across many different callbacks with complected concerns, or one must endure a great deal of ceremony with models, controllers, view models, and views/templates to structure an application.</span> <span>Ideally when we build a web application all we should have to do is describe how our application's data should be represented on the DOM.</span> <span>We shouldn't need to worry about callbacks, twiddling the attributes of particular elements, or updating cached state.</span><br><br><span>As it turns out, ClojureScript's rich data structures and semantics allows us to easily write such simple, declarative code.</span> <span>I will discuss these ideas using examples from visualization-rich dashboard applications.</span><br><br><span>Recommended reading:</span><br><br><span>C2:</span> <a href="http://keminglabs.com/c2/" target="_blank">http://keminglabs.com/c2/</a><br><span>Knockout.js:</span> <a href="http://knockoutjs.com/" target="_blank">http://knockoutjs.com/</a><br><span>Rich Hickey's talk on the benefits of immutability:</span> <a href="http://www.infoq.com/presentations/Are-We-There-Yet-Rich-Hickey" target="_blank">http://www.infoq.com/presentations/Are-We-There-Yet-Rich-Hickey</a></p> |
→ |
<p><a href="http://keminglabs.com/">Kevin Lynagh</a> will talk to us about data-driven web applications with ClojureScript:</p>
<p><span>A web page or application is, at its core, just a visual representation of data that people can read, look at, and manipulate.</span> <span>Typically the mapping between the abstract data and elements on the screen is implicit in the code: take some piece of the data, do X here, do Y there; when the user clicks on that thing, modify the page here, and so on.</span></p>
<p><span>Reasoning about such code is difficult: either control is inverted across many different callbacks with complected concerns, or one must endure a great deal of ceremony with models, controllers, view models, and views/templates to structure an application.</span> <span>Ideally when we build a web application all we should have to do is describe how our application's data should be represented on the DOM.</span> <span>We shouldn't need to worry about callbacks, twiddling the attributes of particular elements, or updating cached state.</span><br><br><span>As it turns out, ClojureScript's rich data structures and semantics allows us to easily write such simple, declarative code.</span> <span>I will discuss these ideas using examples from visualization-rich dashboard applications.</span><br><br><span>Recommended reading:</span><br><br><span>C2:</span> <a href="http://keminglabs.com/c2/" target="_blank">http://keminglabs.com/c2/</a><br><span>Knockout.js:</span> <a href="http://knockoutjs.com/" target="_blank">http://knockoutjs.com/</a><br><span>Rich Hickey's talk on the benefits of immutability:</span> <a href="http://www.infoq.com/presentations/Are-We-There-Yet-Rich-Hickey" target="_blank">http://www.infoq.com/presentations/Are-We-There-Yet-Rich-Hickey</a></p> |