40 points | by mpweiher 4 days ago
6 comments
Why use eta rather than just lit-html template literals? They have ssr versions of everything, as far as I'm aware.
You might also consider data-star.dev rather than htmx
SSR for Lit is not exactly easy at the moment. The decision to use ETA templates to render HTML is to keep the app as simple as possible where ever simplicity is an option.
The Lit component which renders HTMX and calls a global helper function is described as “self contained, stateful unit”…????
yeah, not really "self-contained" bc it depends on HTMX and a global helper (updated the post).
Excuse my ignorance, but this seems to me like a poor man’s SvelteKit with extra steps and less features?
It’s a bit more lightweight (in terms of client-side JS), and avoids front end state unless absolutely necessary.
One of the key moves is keeping state on the server. The front end ends up being much simpler and less bug prone.
Why use eta rather than just lit-html template literals? They have ssr versions of everything, as far as I'm aware.
You might also consider data-star.dev rather than htmx
SSR for Lit is not exactly easy at the moment. The decision to use ETA templates to render HTML is to keep the app as simple as possible where ever simplicity is an option.
The Lit component which renders HTMX and calls a global helper function is described as “self contained, stateful unit”…????
yeah, not really "self-contained" bc it depends on HTMX and a global helper (updated the post).
Excuse my ignorance, but this seems to me like a poor man’s SvelteKit with extra steps and less features?
It’s a bit more lightweight (in terms of client-side JS), and avoids front end state unless absolutely necessary.
One of the key moves is keeping state on the server. The front end ends up being much simpler and less bug prone.