Front End

Backbone → React: it's a people problem after all ?

Backbone → React – Step 1

A puzzle in JavaScript objects

This is a puzzle you can run into if you’re not careful, and sometimes, despite your best efforts, even if you are careful. It happened to me when I had a settings object that I passed into a view. The view then did things. When I made a new view from the settings object, it looked like the view I had just cleared.

Work on React+D3js ES6 v2 begins in earnest

Backbone with ES6

How to add ESLint to your project

Livecoding #21: Use Babel for libraries, not Webpack

Animated string diffing with React and D3

Livecoding #20: You can’t extend an object

Conway’s game of life in Google Docs

Livecoding #19: It’s hard to package a library

JavaScript can fetch() now and it's not THAT great

I broke AJAX in Chrome 52 ?

JS object optimization bug in Chrome 52

Livecoding #18: An abstract React transition component

Livecoding #17: Particle physics is hard

Livecoding #16: canvas.drawImage performance is weird but magical

Livecoding #15: Reaching the limits of canvas redraw speed

Livecoding #14: Mostly-smooth animation up to 4,000 elements with React and canvas

Livecoding #13: rendering React components with canvas

Livecoding #12: towards animating 10k+ elements with React

Using d3js transitions in React

How to Make a Piechart using React and d3

Animating with React, Redux, and d3

Don't Worry; It's a Compiler Bug

There's a "bug" in ES6 modules

React+Flux can do in just 137 lines what jQuery can do in 10

React components as jQuery plugins