The other day I was asked to examine a performance issue on an Angular 11 app. Simply typing in an... Tagged with javascript, webdev, webcomponents, performance.

Dev.to is a community platform for developers, offering resources, discussions, and networking opportunities to empower individuals in their coding journey. Developers can learn new programming languages, frameworks, and tools, engage in discussions on best practices, and share their experiences with fellow developers to enhance their skills and grow their professional network.

A performance issue in an Angular 11 app was caused by a CSS rule, not JavaScript. The article discusses the use of JavaScript in web development and the importance of optimizing static assets and JavaScript bundles. It also addresses the role of Web Components and the Shadow DOM, concluding that excessive use of JavaScript is the problem, not JavaScript itself.

JavaScript is not the problem

Must all the web work without JavaScript?

Does this mean js-based framework is still bad?

Great post! It demonstrates how small details can have a big impact on application performance. It’s interesting how the author investigated and discovered that the problem wasn’t where it initially seemed to be. It’s definitely a good lesson on the importance of thorough investigation into performance issues.

I think Chris’ message is misunderstood. It’s not that “JS is bad” or even “JS is overused”. What I understand from his message is that we tend to do everything with JS, even what already works on its own with HTML or CSS.