Anti-frameworkism: Choosing native web APIs over frameworks

Modern web browsers now handle many tasks that frontend frameworks were originally designed to address, such as component encapsulation, dependency management, and complex layout creation. Despite these capabilities, developers often default to using frameworks like React, Angular, or Vue, primarily for convenience, even though they can negatively impact performance, SEO, and page weight. The debate between "frameworkism" and "anti-frameworkism" highlights the choice between starting projects with a framework or leveraging native web APIs first, introducing frameworks only when necessary. Native web technologies like Web Components, ES modules, and modern CSS now offer robust solutions for many common development needs, reducing the necessity for frameworks in numerous scenarios. While frameworks can streamline developer workflows, they often introduce significant overhead, making them less suitable for projects where user experience is prioritized. The "DX vs UX trade-off" suggests that while frameworks improve developer experience, they can detrimentally affect user experience due to increased bundle sizes and slower load times. Alternatives like Preact, Lit, and Alpine.js offer lighter, more efficient options for developers looking to strike a balance between performance and ease of development. The article advocates for a problem-first approach, emphasizing the importance of understanding native web APIs and choosing technologies based on real-world impact rather than trends, even as the job market continues to favor framework-heavy skills.