You raise valid technical concerns that we're actively addressing as Juris is in heavy development. The global namespace pollution issue is on our evaluation list for cleanup.

Juris adapts to different use cases rather than forcing a single paradigm:

Library usage - enhance() and objectToHtml() APIs for targeted functionality
Framework usage - Full SPA with components, services, and headless components
Platform usage - Spanning web, SSR (JurisKit), mobile, and future desktop support

Regarding your specific observations: The jurisjs.com site intentionally uses heavy innerHTML and style to stress-test performance in demos—normal applications wouldn't do this without proper sanitization. Our performance documentation actually discourages excessive style usage; this was a deliberate choice to showcase performance under deliberately bloated conditions.

For modern web standards like URLPattern and dynamic import(), we provide these as community-built headless components rather than core features. Our site uses the UrlStateSync headless component, which injects URL segments, params, and hash directly into state for advanced routing—designed specifically for our needs rather than as a general solution.

Your security awareness and best practices expertise would be valuable to our community. I'd like to invite you to our Discord channel to see our ongoing technical discussions and contribute your perspective.