I've recently been learning React and Redux Sagas for a new project I'm joining. It's been fun transitioning from Angular and learning what project organization looks like without an opinionated framework. As I looked through the code I started to notice that yield is used a lot to generate values and pass those values to the Redux store using redux-saga. I haven't worked with yield yet so I needed to do some research.
I love working on the full stack of technologies involved with developing an application. It's satisfying to design and implement a feature on the backend and request the data from the frontend application to render out something awesome. It's very rewarding but it can be a long process to set everything up. It's often a boilerplate experience and I often find myself doing a lot more devops than development. This got me looking for alternative ways to setup servers and systems that could aleviate this need to iterate on systems rather than programs.
I've recently been unfortunate enough to work on the impending migration away from AngularJS toward the new Angular. Eventually AngularJS will be officially deprecated by the Angular team once Angular 2+ overtakes its predecessor. When that happens, security vulnerabilities may keep AngularJS from being used in production apps. This means now is the time to get out! I've recently been learning Angular with TypeScript and just want to say I really hate every single build system I've seen thus far.
Learning React has always seemed daunting to me. I've downloaded several ‘quickstart’ projects in the past and quickly become overwhelmed. With the huge chain of dependencies I wasn't able to get a clear picture of how it all worked. So I dropped it. I still used Ramda and other functional programming libraries, but I just passed React by because it wasn't approachable. Then Redux‘s author, Dan Abramov made a post titled “You Might Not Need Redux” in September.