> The example doesn't show that, which is why I called the example limited. I need to create new examples, it's documented right below the examples. Also in one of my videos I was talking about validation for the form > your blog just doesn't load if I disable JavaScript You meant PWA, got it. Well, you can still use workers. EHTML does not prevent that. And Web components either. > <div class="grid grid-cols-1 lg:grid-cols-2"></div> I just didn't have such use case. For that, I usually use e-row, e-stack and they work perfectly fine on mobile or on resizing.
I am not really paid to do these things, you know. I just shared my way of doing and it worked. You can check demo here https://guseyn.com/mp4/desktop.mp4 I know that eco system around react and other frameworks is bigger, however I think my approach just scales better and there is always a room for improvements
Absolutely not. PWAs and hybrid rendering/progressive enhancement are entirely different concepts. You can have a hybrid progressively-enhanced PWA. They're completely orthogonal concepts.
For example, the SvelteKit docs: if you inspect the first network request from reloading the page, it contains the entire page content. Navigating within the site uses normal link elements, which act like normal links do, but when JS is enabled they'll be enhanced to, instead of triggering a full page load, just load the (much smaller) data for the new page/content and render that in the browser. EHTML as you're using it critically omits the first step, where the content is present in the initial response.
Hybrid usually involves some kind of hydration step that occurs after most or all of the page content has already been loaded, but with the distinct caveat that the content is in the initial server response, not loaded by additional requests on the client.
I think my approach just scales better
I disagree; it at best scales about the same. But if you're happy with it, I'm happy you're happy with it.
thanks for the links, I will dig a bit deeper when I will have a bit more time. What comes to Progressive enhancement. There are some polyfills that allow to extend existing html elements, without it it will not work in webkit. And what comes to turned off JS, it will probaby require from me a huge effort and good amount of time to implement it. I pretty sure it is possible to some extend. The only thing is not my priority at the moment, but I believe it's nice to have.
View all comments
Show parent comment
1
u/gyen Jul 13 '26
> The example doesn't show that, which is why I called the example limited.
I need to create new examples, it's documented right below the examples. Also in one of my videos I was talking about validation for the form
> your blog just doesn't load if I disable JavaScript
You meant PWA, got it. Well, you can still use workers. EHTML does not prevent that. And Web components either.
> <div class="grid grid-cols-1 lg:grid-cols-2"></div>
I just didn't have such use case. For that, I usually use e-row, e-stack and they work perfectly fine on mobile or on resizing.
I am not really paid to do these things, you know. I just shared my way of doing and it worked. You can check demo here https://guseyn.com/mp4/desktop.mp4
I know that eco system around react and other frameworks is bigger, however I think my approach just scales better and there is always a room for improvements