The web development community talks a lot about single-page apps, but are we all on a single page? Here's my ontology of apps organized by rendering and navigation.
People talk about htmx as though it's saving the web from single-page apps. Well, I guess I missed the memo, because I used htmx to build a single-page app.
How I built a local-first app for planning trips, and what I learned about the current state of the local-first ecosystem along the way.
Web components won't take web development by storm, or show us the One True Way to build websites. What they will do is let us collectively build a rich ecosystem of dynamic components that work with any web stack.
A one-dimensional spectrum can't sufficiently capture the tradeoffs involved in web development.
Web components can dramatically loosen the coupling of JavaScript frameworks. To prove it, we're going to do something kinda crazy: build an app where every single component is written in a different JavaScript framework.
The world is poorer when friable foundations lead to crumbling creations. But it is poorer still when we are so concerned with the foundations that we never create at all.
If we're building things that we want to work in five or ten or even 20 years, we need to avoid dependencies and use the web with no layers in between.
State-based CRDTs grow monotonically, but that doesn't mean they can't be efficient. We'll learn how to compress the pixel editor state by 98%.
CRDTs sound cool, but how are they actually used? Let's learn by building a collaborative pixel art editor.
CRDTs don't have to be all academic papers and math jargon. Learn what CRDTs are and how they work through interactive visualizations and code samples.
Two weeks at Recurse went by fast! I started out trying to build an Audio Units extension and — in a classic yak shave — ended up building a live coding audio playground.