I believe a part of this is due to a pipeline issue. I wanted to become a web developer about seven years ago. I decided to read articles, watch videos, and att

I believe a part of this is due to a pipeline issue. I wanted to become a web developer about seven years ago. I decided to read articles, watch videos, and attend some online courses to learn all about it. I even decided to join local developer sessions to see what the community is actively engaged in. Not once did I ever see or hear about developing a website as a traditional multi-page site (MPA). Literally everything was about SPAs. React, webpack, etc. Naturally, I wanted to ensure I was learning employable skills. I didn't want to learn how to make MPAs when that methodology is soon to be obsolete and going away like the dodo bird — or so I thought. Sadly, I think many new devs are like me. They follow an online tutorial and learn how great a framework like Django is. But the tutorial guides them into serving the site as an SPA, completely ignoring the fact that Django has a highly practical and powerful built-in template system that makes web development easy for most use cases! This has left an impression on me that this community has a "shiny object" problem. We throw away perfectly good tools and methodologies for the next great thing without thoroughly thinking through the use case to see if the increased complexity is justifiable. There is nothing wrong with SPAs. It's just that they have become the hammer and nail problem. Not every website should be an SPA. Just like how every website shouldn't be a MPA.