A logical choice for a CMP
Using plain JavaScript for a CMP is a logical choice. All third-party services involved in consent already work this way: analytics, advertising, external widgets.
A CMP operates in the browser. It must interact with the DOM, block scripts, and handle events. JavaScript is the natural tool for this.
Compatibility first
tarteaucitron is used on a wide range of websites, often institutional ones. Browser compatibility is therefore a strong constraint.
For a long time, very old browsers were supported. Some are no longer, but the goal remains the same: work everywhere without surprises.
Simplicity and performance
The project has no third-party dependencies. This reduces failure points and simplifies maintenance.
Everything loads quickly, usually in under 100 ms. This level of performance is hard to achieve with unnecessary layers.
An assumed choice
This positioning may seem old school. It probably is. But it works, it is stable, and it remains understandable over time.
For tarteaucitron, this feels like a healthy balance 🙂
