Throughout your adventures with Angular, you will undoubtedly come across situations where custom directives make sense. These situations typically involve DOM manipulations, or calling a jQuery plugin.
AngularJS has been instrumental in changing the way I develop web applications. From building imperative views where both business logic and user interaction live, to separate controllers and directives that handle both requirements respectively. From sharing components through jQuery plugins, the usual common denominator, to sharing components through declarative HTML. From reacting to model changes through events, to wiring up the HTML to react to model changes. The list goes on.
Just when you think that you're in control,
Just when you think that you've got a hold,
Just when you get on a roll,
Here it goes, here it goes, here it goes again.
OK Go - Here It Goes Again
One of the main benefits of Angular is the ability to easily extend HTML with new behaviours through the use of custom directives. Directives allow developers to match markers in the DOM with the intended behaviours.
I’m a big fan of CoffeeScript. It makes working with Backbone.js so much nicer than doing it in VanillaJS.
There is a JS Jabber that came out recently that focused on Backbone.js. The cast featured Jeremy (developer for Backbone.js) and Yehuda (developer for Ember.js), and touches on some interesting points:
I recently started working on pipelines using Hadoop to run MapReduce jobs. One of the pipelines I need to setup involves reading in two or more text-delimited files (e.g. CSV), join them on one or more fields (inner, outer, left, or right), then write out the resulting text-delimited file.
I added searching capabilities to this static website. I don’t think any website is useful these days without some basic search functionality.