>Does a browser really have to be so complex that it warrants updates more often than the very sites that are being browsed? Contrast this with the design of id

>Does a browser really have to be so complex that it warrants updates more often than the very sites that are being browsed? Contrast this with the design of idk MP3: a relatively simple and ultra-stable decoder app with a large variety of backend pipelines that can create MP3s. The problem is the recent trend that everything has to be a web application. So browsers aren't just to access information anymore, but literally to do everything else too. I personally don't agree with the web application trend, but this is the reason why a browser is so much more complex compared to an MP3 decoder: the decoder has to do a single thing, the browsers have to do more and more things.