From Mixins to Custom Hooks: History of Sharing in React w/BenMVP

👉RSVP NOW FOR AN INVITE TO THIS MEETUP VIA ZOOM

Click the link above to fill out your details on Zoom so you can get an invite.

After registering, you will receive a confirmation email containing information about joining the meeting.

React’s component-driven design simplifies reusing UI because chunks of markup can be encapsulated into custom components. Likewise, sharing traditional data utilities is straightforward because React is “Just JavaScript”™. But what about sharing non-visual component logic like state shape and lifecycle methods? React has had several approaches over its lifetime to solve this problem: mixins, higher-order components (HOCs), render props, and now hooks, each with its pros and cons.

In this session geared towards current React developers, let’s take a history lesson on sharing in React in order to better understand how modern-day custom hooks work and the problems they solve. By the end, not only will we know how hooks function, but we’ll also be equipped to pull out non-visual component logic into easily shareable custom hooks in our apps.

👉RSVP NOW FOR AN INVITE TO THIS MEETUP VIA ZOOM

About the Presenter:

Ben Ilegbodu is a Christian, husband, and father of 3, with over 15 years of professional experience developing user interfaces for the Web. He currently is a Frontend Architect at Stitch Fix on their Frontend Platform team, helping develop their Design System and build out their Frontend Infrastructure (aka DivOps). Ben also is a Google Developer Expert and enjoys playing basketball, DIY, watching movies, and tweeting (@benmvp) / blogging (benmvp.com) about his experiences with new web technologies.

This event is sponsored by ChiselStrike.

ChiselStrike provides everything you need to handle your backend, from the data layer to the business logic, wrapped in powerful abstractions that let you just code and not worry about handling databases schemas, migrations, and operations again.

It allows you to declaratively specify compliance policies around who can access the data and under which circumstances.

Your ChiselStrike files can go into their own repo, or even better, into a subdirectory of your existing frontend repo. You can code your presentation and data layer together, and turn any frontend framework into a full-stack (including the database layer!) framework in no time.

ChiselStrike will be doing a Workshop Soon! How to create a complete custom backend application in minutes using only TypeScript.

We strongly encourage you to join their DISCORD Channel and learn how to handle your backend, from the data layer displayed on the frontend. https://discord.com/invite/GHNN9CNAZe

From Mixins to Custom Hooks: History of Sharing in React w/BenMVP image

👉RSVP NOW FOR AN INVITE TO THIS MEETUP VIA ZOOM