Eradicate Runtime Errors in React with Flow
Flow is pretty awesome. Oh, more details… Ok, so, Flow is great for large or growing codebases that could use a hand in the static analysis department. Even outside of the context of React (heh), Flow shines by ensuring type safety across modules; that is, it allows you to annotate variables, functions, et al. with type annotations that Flow can parse and use to spot errors in your application before they happen.
Where Flux Went Wrong
Already comfortable with the history around ReactJS and Flux? Skip to Flux and Component State to jump right into the problem statement. Ahem. When ReactJS first entered the development scene it attracted front-end developers across the world with its promise to introduce some semblance of sanity back into the dreaded Single Page Application. The framework, commonly referred to as the V in MVC, popularized the concept of componentized applications; that is, everything you see on the page is a React component.
From Redux to GraphQL
Here’s the deck from a presentation I recently gave that convinced our team to pivot from a Spring/Java REST backend to Relay and GraphQL. Since I don’t have the time right now to really write a blog post on anything, I figured this was better than nothing! http://slides.com/davidzukowski/deck/fullscreen