Sounds about right. Want a chart that doesn't look completely shit? Well it's an integration.
Templating, Jinja used for html with placeholders is fine, anything else should be provided in the context already. But used as view controller, like HA, oh hell no.
The debugging issue is also a HA footgun, in Django/Jinja, you get proper stack traces and exceptions with tracebacks, I even recently let Claude generate a SQL repeated query analyzer that pierces through this (transpiled template to Python to bytecode have mismatched line numbers/signature) and maps the call sites back to templates with accurate line numbers, if some template causes select one row in a loop issue.
Seems like it's popular and best of the competition - not that hard as most are closed source appliances/devices, but still rather shit. Sad, but it's a way too chonker project to rewrite / redo even with infinite tokens to burn.
Templating, Jinja used for html with placeholders is fine, anything else should be provided in the context already. But used as view controller, like HA, oh hell no.
The debugging issue is also a HA footgun, in Django/Jinja, you get proper stack traces and exceptions with tracebacks, I even recently let Claude generate a SQL repeated query analyzer that pierces through this (transpiled template to Python to bytecode have mismatched line numbers/signature) and maps the call sites back to templates with accurate line numbers, if some template causes select one row in a loop issue.
Seems like it's popular and best of the competition - not that hard as most are closed source appliances/devices, but still rather shit. Sad, but it's a way too chonker project to rewrite / redo even with infinite tokens to burn.