Let's Code JavaScript - The Lab

HDRips | MP4/AVC, ~1001 kb/s | 1280x720 | Duration: 13:07:41 | English: AAC, 66 kb/s (1 ch) | 7.41 GB

Genre: Development / Programming

Experimentation, exploration, and general messin’ about. Here in The Lab, we try out new tools, create new ideas, and see what we can break. Anything and everything that doesn’t fit in the other channels could end up here.

Front-End Frameworks: Ember.js (Part III)

We wrap up our exploration of Ember.js by building out custom form fields, setting up events and cross-application communication mechanisms, and dealing with performance. In the end, is Ember.js a good choice for your front-end applications? We decide.

Front-End Frameworks: Ember.js (Part II)

We continue our investigation of Ember.js with a look at its influence on design and architecture. We build out our stock market projection components and hook them up to our intentionally-quirky domain layer. How easily does Ember integrate with existing business logic, and what does it take to test an Ember component? We find out.

Front-End Frameworks: Ember.js (Part I)

Ember.js is a framework for, in their words, “ambitious web applications.” But is it going to cause more trouble than it’s worth? We start a three-part deep-dive into Ember. In this episode, Ember fundamentals. We look at a “Hello World” app, components, modularity, testing, and the challenges of escaping Ember’s assumptions.

Front-End Frameworks: AngularJS (Part III)

We conclude our investigation into AngularJS’s impact on design and architecture. In this episode, we bring in our pre-existing persistence layer and use it to coordinate changes across our application. We also create a custom form field that uses domain-driven validation. Does AngularJS play well with our architecture? Should you use it? We render our verdict.

Front-End Frameworks: AngularJS (Part II)

We continue our exploration of AngularJS with a look at application design and architecture. Angular assumes simple models that live in “scope” objects. Our sample application, though, has a rich domain layer based on Ward Cunning