You might have heard about features like “Hooks”, “Suspense”, and “Concurrent Rendering” in the previous blog posts and talks. In this post, we’ll look at how they fit together and the expected timeline for their availability in a stable release of React.
In our previous post A introduction to Web Components we learned the basics of the APIs that when used together can create a compelling and reusable way to make UI components. We learned Web Components communicate primarily via properties and events. Web Components can also use the Shadow DOM API to create template and CSS encapsulation. In this post we are going to look into a project ran by Polymer called lit-html.
Few things in the frontend world are as hot as Design Systems, the idea of building a design spec or library of reusable components that can be shared across a team or company. Design Systems enforce style and branding guidelines, reduce design fatigue for engineers, and consolidate component engineering to one single set of components and a team that builds them. Basically, they help teams manage design at scale.
Given that coordination and communication swamp all other costs in modern software development it is a pressing area to invest in, especially as your team scales. I use a framework of a Small Number of Well Known Tools to build shared understanding in our complex systems over time. When we want to do something other than use the Small Number of Well Known Tools (in the small number of well known patterns), that’s a Departure. I have a long note I want to post on technical decision making and departures. In the mean time I want to share a short list of questions I’ve been using in various forms for over a decade to engage with The Dreaded Question.