The Code Experience

Reading Hacker News comments on JavaScript frontend articles is a depressing task these days. The majority is complaining: Tooling too complex, bundling too complex, Too many different frameworks, best practices change too quickly.
Spearheading: The React ecosystem. Completely modular with an abundance of libraries, patterns, and abstractions, pushed by an enthusiastic, Facebook-backed community eager to iterate on best-practices over and over....

I have been writing React/Flux applications for a year now. Looking back at one year of Flux development I can clearly say that this Flux thing works. Past are the days of "I'm not touching that event chain". All the Flux codebases I have worked on were...

At my company, we recently finished the fifth iteration over a medium sized, but very interactive and graphical web-app.
We started a first prototype with Backbone and as the project got bigger, expanded to Chaplin with d3.js. Some time ago, we started to use React and liked it so much that we ended up with a pure Flux-React implementation....

Our company put the approach I outlined in this post into production roughly 6 weeks ago. Recently, I dove back into our Flux application, having not looked at it for a couple of weeks.
Returning to a project after a longer hiatus is - in my experience - one of the best moments to figure out the weaknesses of your codebase: You have partially mitigated the curse of knowledge by occupying your brain with other things....