The open source community came to the rescue, and a year later, we have dozens of Flux libraries, and even some meta-projects aimed at comparing them. True to their word, their implementation was really simplistic, and involved writing a lot of verbose, repetitive boilerplate to get things going. To make things even more interesting, Facebook stated that Flux is a “pattern,” not a framework, and their implementation of Flux is just one example of the pattern. Sure enough, Facebook (creators of React.js) had one more ace in the hole: The Flux workflow, which promised to fill in the missing “M” and “C” functions. How do I fill in the missing pieces? Should I write my own? Should I just use an existing library? If so, which one? But React always marketed itself as the “V” in “MVC.” This caused some amount of frustration among web developers, who are used to working with complete frameworks. This anxiety among developers played into the hands of React, which was seeking to establish itself in the community. What does that tell someone who want’s to start a new web project? Do you want to write your new project in a framework that is going to be made obsolete by a new version release? The team announced that, first, Angular 2 will be completely different, without a clear migration path from Angular 1, and, second, that Angular 2 won’t be available for another year or so. It seems Angular became a victim of the Osborne effect, or “death by pre-announcement”. I even started seeing Angular in very conservative corporate environments, and I took it’s bright future for granted.īut suddenly, a strange thing happened. During those two years, Angular really gained a foothold among JavaScript developers, and almost became synonymous with modern JS development.

When React.js was released two years ago, I was just learning Angular, and I quickly dismissed React as some obscure yet-another-templating-library.

Being able to identify a tool that is going to stay relevant for at least another year is becoming an art itself. A library can go from early-adopter toy, to state-of-art, to obsolescence in the course of a few months. The speed of innovation in JavaScript Land is so high, that some people even think it is counter-productive.

Backbone js tutorial 2015