Notes

I don’t like the fact that libraries like React are so heavily used, but over the years, I’ve grown more empathetic about the decision by teams to use them. The web platform doesn’t currently give us all the tools we might need, but I’m hopeful it will in the longer term. I also get that people can’t wait for that and need to get moving, so libraries service their needs better than the web platform currently does.

Definitely agree here. For bigger & more complicated projects, libraries can provide a lot of help to get it off the ground quickly. Necessary, no, but from a practical perspective I get it. Managers and higher ups don't necessarily always care about what is best, they care about the bottom line and having something to ship.

All I would say is finding the lowest-tech solution and leaning into browser capabilities as much as possible is a good way to build something resilient and reliable.

Completely agree, if you can avoid over-complicating your builds with libraries and sticking with HTML & CSS, go for it.

So there’s very little indication any of these problems are going to slow down. Consumers are going to be forced to pay higher and higher rates for increasingly deteriorating services, to the point where piracy is going to become an increasingly alluring value proposition. And when that happens, you can be absolutely, indisputably assured that executives will blame absolutely everything but themselves.

Wil Wheaton put it perfectly when he said that many people would pay for content if it’s easy and cost effective. Jack up the prices, make it difficult to find the content you want, and the results shouldn’t be surprising.

Writing HTML in itself isn’t that hard, no.

But: building user interfaces by elegantly composing this language’s features with CSS, creating pleasant designs and user experiences worth remembering requires experience and skills that should not be underestimated. Neither should HTML; it’s one of the languages—if not the most important one of them all—that shape the web.

Web browsers can be incredibly forgiving in terms of displaying content to the user, so mistakes can go unnoticed. But those mistakes can cause problems with accessibility and many other things. Writing good, accessible HTML takes skill and should never be discounted.

Build something that matters to you, at least a little bit. The classic is to make yourself a personal website. That’s real. That means the things you learn you can attach to a real project.

I’ve always felt I learn better when I have something real to build. Another todo app that sits around and clutters my file system is good and all, but the lesson feels muted.

Content moderation at scale is utterly impossible to get ‘right’, where the online crowd and journalists and politicians all agree you’ve done the correct things. This doesn’t absolve sites from having to try, to do the best job they can under the circumstances. But it should make us a bit more sympathetic when we see stories about how terrible some site’s efforts at moderation are.

It's one thing to get things wrong from time to time. It's going to happen and we shouldn't always pile on them for every little mistake.

I don’t know the answers to any of this! The point I want to emphasize is that all of this is impossibly nuanced, impossibly complex, and impossible to do in such a way that satisfies everyone. You still have to draw a line somewhere, but be prepared to get yelled at anyways.

I'll leave finding the answers to people smarter than me, I'd just like to see a legitimate effort.

This is actually a pretty cool use for web components and I might have to steal this for my photography site.