I think they solve different problems. I love independent websites, and the web is an amazing medium for serving stateless content. But I think web3 compliments it really well when you want to do something that hooks into a larger, stateful ecosystem.
I think it really depends on what you want to do. If you want build a comment system for your website, then web3 is totally the wrong tool for the job. If you want to write an application that coordinates data across multiple websites, and you're worried about servers going down or APIs changing, then it's a little trickier to think of a simpler way.
