Julian Burr

The web comes accessible out of the box, we just need to know how to use it. With modern advancements in HTML, CSS, and even JS, the tools to build an inclusive experience are more powerful than ever. 

More accessibility means increased usability for everyone, so let’s explore these new tools and best practices, and how they can help us create a better and inclusive web.

With the active TC39 proposal in play, I think it’s about time we talk about Signals.Over the years, the concept has had many different names. From “observables” in KnockoutJS, to “refs” in VueJS, before Solid made “signals” popular. We’ve seen the carcinization of frontend frameworks in the pursuit of more seamless and fine-grained reactivity in our applications.But what actually are Signals? Why do we keep coming back to them? And where does React fit into all of this?

As the pendulum of web development swings back towards the server, streaming has become increasingly popular. Specifically, out-of-order streaming through features like React Suspense, the magical powers behind Server Components.

Let's build our very own simplified version to explore how it works, what problems we are trying to solve, and what this future of web development looks like.

As the momentum of web development swings back towards the server, streaming is becoming increasingly popular. Specifically, out-of-order streaming with features like React Suspense — one of the magical powers behind Server Components.

Let's build our very own (simplified) version to explore how it works, what problems we are trying to solve, and what this future of web development looks like.