> When you build websites you are creating code for others to read as much as you're creating an "app" or document. That's an approach people are certainly wel

> When you build websites you are creating code for others to read as much as you're creating an "app" or document. That's an approach people are certainly welcome to take, and I'm glad that some people do, but I disagree that this is what the act of building a website entails. This feels a bit like romanticizing the early days of the web, when the primary form of learning involved reading other people's source code. The depth and breadth of ways to learn in 2024 looks nothing like those early days. If I choose to build something to solve a particular need or to communicate something I care about, it's my choice as to how I do that. > It's the very essence of what's good and special about the web. The very essence of what's good and special about the web is the diversity of solutions, the myriad of entry points to becoming a web developer, the existence of tools ranging from vanilla HTML/CSS all the way up to complex frameworks like Tailwind, and your freedom to pick your path. Tailwind's existence does not threaten the layers underneath it.