Frameworks are great tools to help relieve developers of having to constantly reinvent the wheel and rewrite code. When a project needs to be deployed efficiently and effectively, a framework will go a long way to helping your developer team make it happen.
1. If What You’re Working on Is Simple
If the goal of the project is to keep it simple, don’t bother with a framework.
2. When HTML and CSS Alone Will Do the Trick
Remember, frameworks are used to abstract some of the more complex aspects of development. With the release of ES6, a number of new features (such as default parameters, template literals, multi-line strings, destructuring assignment, enhanced object literals, and arrow functions — along with modules and classes), reduces the need to even bother with frameworks for many use cases.
Prior to ES6, working with things like classes was a major challenge, even though previous iterations were designed to specifically support classes.
4. If Creative Freedom Is Your Jam
From the official HTMX website, we see this example:
In this example, when a user clicks a button, an HTTP POST request is issued to /clicked, and then the response is used to replace the element using the parent-div from within the DOM.
Two of the main reasons for using a framework are speed and the integration of external data sources. If neither of those is an issue with your project, then a framework is only going to get in your way and squash your creativity.