I've organized the Clojure Cup a couple of times now: The inaugural event in September 2013 and the second edition in September 2014.
I'd very much like to see a Clojure Cup 2015 this fall, but the time has come for me to hand over the reins to someone else. So, I'm looking for someone to take on the ownership and organizing duties of Clojure Cup.
Since you can't keep up with it, you have to choose what to focus on. And having to make that choice is a cause of anxiety in itself. Are you focusing on the right things? Is the framework you're learning the best one for you or is there something even better out there? Will something happen next month that'll make your choices seem obsolete?
There are ways to resist these feelings of fatigue and anxiety. Here's what works for me.
I've always had a problem with transclusion. Though I've used it from time to time, using it always felt uncomfortable. I was never really sure what exactly the API was doing, or more importantly, what exactly I was supposed to do when using it.
Based on what I've heard, I'm not alone in this. Transclusion is one of those things people often mention when they talk about their difficulties with Angular.
What is it that makes this a difficult topic then? Conceptually we're not talking about anything hugely complicated - it's essentially just moving some DOM elements around. I think the bigger problems are tangential:
The API is tricky, with its higher-order functions and "magic arguments".
Parts of the API are deprecated, and it can be hard to figure out which parts.
The documentation uses lots of big words ("a transclude linking function pre-bound to the correct transclusion scope").
There are actually two separate features provided by the same API: Regular transclusion and element transclusion.
It wasn't until writing the transclusion chapter for my book that I felt I had fully grasped this topic. While the book covers the internals of the API, this article is an attempt to write the user guide I wish I'd had before. I want to describe what you can do with transclusion and how you can do it.
One can compare these frameworks in various ways, but I think one of the most interesting differences between them is the way they manage state. In particular, it is useful to think about what these frameworks do when state changes over time. What tools do they give you to reflect that change in your user interface?
Managing the synchronization of app state and the user interface has long been a major source of complexity in UI development, and by now we have several different approaches to dealing with it. This article explores a few of them: Ember's data binding, Angular's dirty checking, React's virtual DOM, and its relationship to immutable data structures.