đ Welcome to our fourteenth issue! This week we have a new React release candidate, new libraries, and new conference talks to peruse. I hope you find something valuable! Take care. â Jake
Quote of the Week
âDevelopers are your canary in the coal mine for user experienceâ because they create the damn things!â âShawn Wang, Slack is Fumbling Developers
From the official React blog, hereâs the announcement for a release candidate of React 17. The headline is eye-catching: this release doesnât include any new features and few breaking changes. So whatâs going on? From the announcement: âthis release is primarily focused on making it easier to upgrade React itself.â
If Rome, a new library by Sebastian McKenzie, lives up to even some of its ambitions, the terrain of JavaScript tooling could change. Rome is aiming to âunify the entire frontend development toolchainâ providing a linter, compiler, bundler, test runner, and more. Very exciting!
Paperclip is: âa language for UI primitives that allows you to build React applications more quickly, and with fewer CSS bugs.â Styles are defined in a .pc file, and imported into your component. With a Storybook-like preview feature, isolated styles, and TypeScript integration, this looks promising!
Hungry for some fresh React conference talks? Check out the React Rally 2020 Live Stream, recorded on August 14 on YouTube. Topics covered include: âReact Native, state management, animation, community, universal JavaScript, and so much more.â
Consider this post from Max Rozen a cheat sheet to the common React component libraries of today. If you havenât considered using a component library, you shouldâ the choices are better than ever.
In honor of this weekâs React Rally conference, Iâm including this talk by Justin Falcone from React Rally 2019. Watch as Justin narrates the past and present of web development while demoing his toy-language generator Zebu. Itâs all in the service of a powerful idea: code is a user interface, and the experience it provides matters.
Fragments are a core part of React. They solve a real-world problem: how does one return a collection of children without adding an extra node to the DOM? Iâve always preferred the React.Fragment syntax over the terser alternative.
Do you want to really (really!) learn React, while staying current on this exploding ecosystem? Subscribe to React Explained, a bi-weekly newsletter of amazing, curated React news and resources, simply explained. Itâs free! Subscribe now.