Tag Archives: javascript

Leaving JSPs in the dust: moving LinkedIn to dust.js client-side templates | LinkedIn Engineering

Today, javascript templates are one of the key components of our front-end infrastructure strategy: they enable browser/CDN template caching, they allow for a cleaner separation of presentation tier concerns, and at the same time, they enable greater unification of our front-end stacks across the company.
We are actively building and migrating some of our core properties to client-templates to achieve our overall objectives. The next blog post will focus more on the challenges we faced in embracing dust.js templates, including the solutions we are building to extend dust.js for static content flushing, rendering logic, formatting, i18n, and A/B testing partials.

(Full Story: Leaving JSPs in the dust: moving LinkedIn to dust.js client-side templates | LinkedIn Engineering)

Backbone Fundamentals – A Free Work-In-Progress Book For Developers Of All Levels

Backbone Fundamentals hopes to change that. Whilst still a work-in-progress, my goal is to try adding something new or improving the book in some way everyday. That level of consistency can’t be promised forever, but I want to do my best to centralize the knowledge and experience I (and hopefully some other Backbone users) have learned somewhere that’s easy for developers of any level to just pick up.

(Full Story: Backbone Fundamentals – A Free Work-In-Progress Book For Developers Of All Levels)

JesCov – JavaScript code coverage

JesCov is an open source tool for measuring code coverage of JavaScript. It makes it possible to find out both line and branch coverage from any ES3-compliant source code. It is not tied to any particular testing framework, but the only current integration point is for Jasmine. The general approach is based on a JSON data interchange format, which means some of the reporting tools could potentially be used against data collected in some other way than running the core JesCov project.

(Full Story: JesCov – JavaScript code coverage)

Patterns For Large-Scale JavaScript Application Architecture

Decouple app. architecture w/module,facade & mediator patterns. Mods publish msgs, mediator acts as pub/sub mgr & facade handles security

(Full Story: Patterns For Large-Scale JavaScript Application Architecture)

The pros and cons of developing a complete Javascript UI

Cons1. Javascript Frameworks are still evolving2. Developing two applications instead of one
Pros1. Well thought out and tested API2. Your JS UI code as API reference

(Full Story: The pros and cons of developing a complete Javascript UI)

Patterns For Large-Scale JavaScript Application Architecture

Decouple app. architecture w/module,facade & mediator patterns. Mods publish msgs, mediator acts as pub/sub mgr & facade handles security

(Full Story: Patterns For Large-Scale JavaScript Application Architecture)

The pros and cons of developing a complete Javascript UI

Cons1. Javascript Frameworks are still evolving2. Developing two applications instead of one
Pros1. Well thought out and tested API2. Your JS UI code as API reference

(Full Story: The pros and cons of developing a complete Javascript UI)

d3.js – a small JavaScript library for manipulating documents based on data.

D3 is not a traditional visualization framework. Rather than provide a monolithic system with all the features anyone may ever need, D3 solves only the crux of the problem: efficient manipulation of documents based on data. This gives D3 extraordinary flexibility, exposing the full capabilities of underlying technologies such as CSS3, HTML5 and SVG. It avoids learning a new intermediate proprietary representation. With minimal overhead, D3 is extremely fast, supporting large datasets and dynamic behaviors for interaction and animation. And, for those common needs, D3’s functional style allows code reuse through a diverse collection of optional modules.

(Full Story: d3.js – a small JavaScript library for manipulating documents based on data.)

Backbone.js Tutorial with Rails

Backbone.js really introduces a new kind of data flow for Rails apps. Instead of data flowing like this:
Rails Model => Rails Controller => Rails View
It now flows like this:
Rails Model => Rails Controller => Backbone Model => Backbone Controller => Backbone View

(Full Story: Backbone.js Tutorial with Rails)

Follow

Get every new post delivered to your Inbox.