Javascript Fatigue
Eric Clemmons
2.9K96

It’s 2017 and after successful delivery of several projects in Redux, I found the approach not scaling well because of the unsolved problems: Functional Programming Fatigue (https://medium.com/@alexdixon/functional-programming-in-javascript-is-an-antipattern-58526819f21e), The Absence of Standard Way to Encapsulate Containers Within Containers in Redux (https://blog.javascripting.com/2016/05/21/the-problem-with-redux-and-how-to-fix-it/), The Absence of the Standard Way to Handle Side Effects (I don’t like Sagas, those make restoring application state impossible after closing app).

I found myself switching so many times between FP and class-based MVC. Between single atom Elm-like rendering with tons of action wrapping and unwrapping boilerplate. Between using Snabbdom instead of React to perform fast in Mobile. So, I personally feel that the fatigue becoming worse. It’s Pandemic now.

Like what you read? Give Brian Haak a round of applause.

From a quick cheer to a standing ovation, clap to show how much you enjoyed this story.