DCoder🇱🇹❤🇺🇦

Yogthos's posts Post Back to profile

Top-level

DCoder🇱🇹❤🇺🇦

@yogthos

A Photoshopped image. Four photos of a man putting on progressively more clown makeup, arranged in a circle, with arrows leading from one photo to the next and looping back to the first photo again.
The captions for the photos, from the one with the least makeup towards the one with the most:
- rendering HTML is too slow, move everything to JS
- everything in JS is too slow, prerender all HTML
- prerender all HTML too slow, render some pages on request
- render HTML on request

In the center of the circle, a caption reads “Job Security”.

Like 6 Apr 2023 at 8:14 | Wall-to-wall | Open on ohai.social

5 comments

Yogthos

@dcoderlt 😆

6 Apr 2023 at 12:11 | Open on mas.to

LisPi

@dcoderlt @yogthos The funny thing is, as far as I'm aware, the actual answer to that in HTML is simply frames/framesets/iframes.

Periodic reload also works in iframe documents (https://en.wikipedia.org/wiki/Meta_refresh), no need for messing around with headers for specific paths & whatnot (or Javascript).

And while those don't necessarily play well with accessibility, unlike bespoke Javascript nightmares, they're standard features so work to improve support can be done reliably.

7 Apr 2023 at 17:36 | Open on mastodon.top

Yogthos

@lispi314 @dcoderlt I've been using htmx recently, and I find it works extremely well. You have a minimal amount of js on the frontend to handle patching HTML elements, and then you just send parts of the page you want to rerender from the server.

https://htmx.org/

7 Apr 2023 at 17:56 | Open on mas.to

LisPi

@yogthos @dcoderlt It's certainly an improvement over the heavy frameworks, but the "progressive enhancement" doesn't seem baked into all of its features, so accidentally creating stuff that doesn't degrade gracefully with Javascript disabled seems likely.

7 Apr 2023 at 18:01 | Open on mastodon.top

Yogthos

@lispi314 @dcoderlt yeah that's a potential problem for sure

7 Apr 2023 at 18:01 | Open on mas.to