Website != Web application. The "anti-patterns" are super useful to those of us who are using all of them to create functional cross-platform applications ;) I

Website != Web application. The "anti-patterns" are super useful to those of us who are using all of them to create functional cross-platform applications ;) I feel that there's a disconnect between website devs and webapp devs, and that the latter win when it comes to adding new functionality. The people who want to use the web as a generic platform are the ones that are turning it into an operating system by itself, which by nature is going to cause bloat, but people still think of it as "hey, it's 'just' a web browser!" when in reality they're becoming almost another whole layer of abstraction that allows arbitrary programs to run on any OS. I agree that the adoption of new unnecessary technologies by websites that don't need them makes for a frustrating experience. Like, when I go to a small-town newspaper's website to read an article, I have to wait seconds for the custom font to load, elements pop in and out of existence as third party advertiser code loads, a video somewhere starts autoplaying, I have to click through a GDPR consent form, a cookies-ok form, a "subscribe with your email" screenjacker, social media buttons appearing reflow the text, ......... yeah it's BAD. I think the issues we encounter come from the wheel-reinvention and the fact that web counterparts of existing technology tend to eschew things like security and scheduling in order to quickly catch up.