Top all-time · #5670
Alexander Petros
Personal blog · alexanderpetros.com/triptychwebprogramming
Alexander Petros's personal blog at alexanderpetros.com covers web and programming. Since 2024, 14 different Hacker News readers have linked it 26 times, most often “Triptych Proposals”. No feed was found, so read it on the site itself.
Too few sampled comments (14) to say how often HN recommends it.?
Why HN links it
HN readers link Alexander Petros's Triptych proposals, which aim to move htmx-style ideas, such as PUT and DELETE support on HTML forms, into the HTML spec. They are often cited as a reference in htmx discussions.
Summarised by Claude from a sample of 14 HN comments that link here. Each comment is marked recommending, critical or neutral (citing without judging); how this works.
Most-linked posts?
- Triptych Proposals11 people · 15 mentions · first linked 2024-08-19
- Support Put, Patch, and Delete in HTML Forms5 people · 6 mentions · first linked 2024-08-19
What Hacker News says?
you can support and publicize the triptych project: https://alexanderpetros.com/triptych/ https://github.com/alexpetros/triptych?tab=readme-ov-file
Comment linking /triptych/
on “The Future of Htmx”Submitted Triptych Proposals as a story · 250 points
HN discussion> We're very close to invokers being baseline, and that will take care of plenty of what htmx was designed to do. From what I've seen, invokers without extra code are designed for client side interactivity (e.g. showing a modal), which is orthogonal to the (correct, IMO) use case of HTMX. You shouldn't use HTMX to turn every custom user interaction into a network round trip, you should use it instead of fetching JSO…
Comment linking /triptych/
on “Please just try HTMX”Submitted Triptych Proposals: Putting the "hyper" back in hypertext as a story · 8 points
HN discussionWe are working to integrated some of the ideas of htmx directly into the HTML specification: https://alexanderpetros.com/triptych/
Comment linking /triptych/
on “Marko – A declarative, HTML‑based language”Submitted Three small proposals for putting "hyper" back in the hypertext as a story · 4 points
HN discussionYes! I expect that I will mostly be sticking to `hx-target` though, for the reasons stated above. My interest in htmx is more on the coarse-grained aspects of its interface, not the finer ones, which is a consistent theme in my writings about it [0]. [0] https://alexanderpetros.com/triptych/
Comment linking /triptych/
on “</> Htmx – The Fetch()ening”Submitted Support Put, Patch, and Delete in HTML Forms as a story · 4 points
HN discussionThere are definitely some parts that are common between these that it could be nice to propagate to the standard. https://alexanderpetros.com/triptych/ lists some of them but I'm not certain how specific to htmx it is or how much it apply to the different variants.
Comment linking /triptych/
on “Mesh: I tried Htmx, then ditched it”Submitted Triptych Proposals as a story · 2 points
HN discussionSounds like this app wasn't a good fit for htmx. I have added it to the "On The Other Hand" section on the htmx website: https://htmx.org/essays/#on-the-other-hand Regarding the default swap behavior of "innerHTML": https://htmx.org/quirks/#the-default-swap-strategy-is-innerh... Our proposal to merge htmx functionality into the HTML spec uses outerHTML: https://alexanderpetros.com/triptych/ Also consider datastar, i…
Comment linking /triptych/
on “Mesh: I tried Htmx, then ditched it”Submitted Support Put, Patch, and Delete in HTML Forms as a story · 2 points
HN discussion> About 20 years ago, Firefox attempted to add PUT and DELETE support to the <form> element, only to roll it back. Why? Because the semantics of PUT and DELETE are not consistently implemented across all layers of the HTTP infrastructure—proxies, caches, and intermediary systems. This is incorrect, according to this comment from the Firefox implementer who delayed the feature. He intended the roll back to be tempora…
Comment linking /triptych/form-http-methods
on “Triptych Proposals”Submitted Support PUT, PATCH, and DELETE in HTML Forms as a story · 2 points
HN discussionHey there, good question! Probably worth reading both sections 6 and 7 for context, but I answer this question specifically in section 7.2: https://alexanderpetros.com/triptych/form-http-methods#ad-ho...
Comment linking /triptych/form-http-methods
on “Triptych Proposals”Submitted Support Put, Patch, and Delete in HTML Forms as a story · 1 points
HN discussionthis is a set of proposals by Alex Petros, in the htmx team, to move some of the ideas of htmx into the HTML spec. He has begun work on the first proposal, allowing HTML to access PUT, DELETE, etc. https://alexanderpetros.com/triptych/form-http-methods This is going to be a long term effort, but Alex has the stubbornness to see it through.
Comment linking /triptych/form-http-methods
on “Triptych Proposals”Submitted Triptych Proposals as a story · 1 points
HN discussionwe are working towards incorporating some of its ideas into the html spec: https://alexanderpetros.com/triptych/
Comment linking /triptych/
on “Local First Htmx”maybe check out fixi, our minimalist implementation of generalized hypermedia controls? https://github.com/bigskysoftware/fixi we are hopeful that w/the work of alex petro and the triptych project that we can get some of the core ideas of htmx into the HTML spec itself: https://alexanderpetros.com/triptych/
Comment linking /triptych/
on “Web dev is still fun if you want it to be”https://alexanderpetros.com/triptych/ will hopefully address that.
Comment linking /triptych/
on “Platform Strategy and Its Discontents”Lots of stuff about this article is strange: * The author first describes a mildly convoluted cookie-stripping middleware under "Actually Solving The Problem" and includes the much simpler `SameSite=Lax` cookie under "Defense in Depth" later on. * The author neglects to mention that `SameSite=Lax` is the default on all major browsers (still good to set it, though), which basically blows up the premise of the article…
Comment linking /triptych/form-http-methods
on “CORS Is Stupid”The Triptych Proposals [1] cover a lot of common use cases for submitting information to a server and updating part of a page. Something like that should have been possible to implement early in web history (I perceive some similarity to frames). Modern CSS (and some newer HTML features) also reduces the need for scripting. I very much doubt that "Enabling scripting was a necessary step for interactive websites." (e…
Comment linking /triptych/
on “The 49MB Web Page”
