alexpetros

5 ms·

1.
by alexpetros 2mo ago
Totally, this is part of the problem I'm trying to solve. I wrote a little about these "call to action links" that you're describing in the proposal.[0] The tl;dr is that I think it would be easier to hold the line that
2.
by alexpetros 2mo ago
> Cancel doesn't navigate. In fact, neither of them do. This is correct. The point of the proposal is that you should be able to implement this pattern with just navigations, and that implementing it differently doesn't chang
3.
by alexpetros 2mo ago
What if I want the cancel button to be to the left of the submit button? This is how GitHub lays out those buttons, for instance. There's fundamentally no reason why a button's functionality should be dictated by its position on t
4.
by alexpetros 2mo ago
I'm not entirely sure what you mean by "in-between" element, but that's not what this proposal does. This proposal simply augments the button's existing ability to navigate the current context by removing the need t
5.
by alexpetros 2mo ago
You linked to `formaction`, which allows buttons to control the action of their nested form. This proposal allows buttons to make actions independent of forms, and the blog has an example of how independent button actions compose nicely wit
6.
by alexpetros 2mo ago
> And that's partially because "Cancel" is pretending you're in a desktop app with desktop idioms. No real, actual person designs websites like this. If I click "Edit" on a GitHub comment, it shows me two bu
7.
by alexpetros 2mo ago
> This seems to conflate appearance with semantics. If an element causes a navigation, I make it a link. Neither of my examples work with links. Logout buttons must be buttons because they trigger unsafe requests, and "search"
8.
The Difference Between a Button and a Link(unplannedobsolescence.com)
67 points by alexpetros 2mo ago|51 comments
9.
by alexpetros 4mo ago
Thank you!
10.
by alexpetros 4mo ago
I'm not as familiar with Magic, but I've always been curious if that community has tooling at a comparable level of maturity to Pokemon Showdown.
11.
by alexpetros 6mo ago
For what it's worth, I think that an embedded DSL to represent most expressions tersely is a worthwhile idea to explore—it's just a more expensive one. That's a cost-effective choice at a some levels of resourcing, but not e
12.
by alexpetros 6mo ago
In the blog I link to a Prolog post I wrote in January because I am very interested in the possibility of using Prolog to prove things about the Fact Graph. I have a personal branch where I try to build some tools for it with DCGs. The ni
13.
by alexpetros 6mo ago
In the context of the article, "cheap" means "easy to set up" not "computationally efficient." The article is making the argument that there are situations in which you benefit from sacrificing the latter in fa
14.
by alexpetros 6mo ago
This is a good question! We do it, it works, and it's definitely an advantage of XML over alternatives. I just personally haven't had the time to dig in and learn it well enough to write a blog post about it. In practice I think p
15.
by alexpetros 6mo ago
Author here. I agree with all this, and I think it's important to note that nothing precludes you from doing a declarative specification that looks like imperative math notation, but it's also somewhat besides the point. Yes, you
16.
by alexpetros 11mo ago
So here's the htmx example for click to edit: [0] <button hx-get="/contact/1/edit"> And here's the datastar one, edited for parity: [1] <button data-on:click="@get('/contact/1&
17.
by alexpetros 11mo ago
Yes! 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 abo
18.
by alexpetros 11mo ago
> Why bother with v4 at all? If it dilutes that simpler interface? v4 makes almost no changes to the interface, other than to flip inheritance to be off by default. > I think that even with req/resp morph leads to a simpler major
19.
by alexpetros 11mo ago
> why use HTMX when it really seems like (a heavier) Datastar-lite? The reason to use htmx is that it has a simpler interface optimized for the majority use-case. With htmx, you are largely tied to a request/reply paradigm. Somethin
20.
by alexpetros 11mo ago
Altering the presentation layer is possible precisely because HTML is a semantic API definition: one broad enough to enable self-description across a variety of domains, but specific enough that those applications can still be re-contextu
21.
by alexpetros 11mo ago
> I worked for a company that was all hateoas. In the formal sense, explicitly structured around the concept, not the sense that html has both data and actions via links, it worked, it was a real product, but it was slow and terrible to
22.
by alexpetros 11mo ago
> HATEOAS would mean your browser/client would be entirely responsible for the presentation layer, in whatever form you desired, whether it's buttons or forms or pages or not even a GUI at all, such as a chat interface. Browser
23.
by alexpetros 11mo ago
> Purists have long claimed that a “truly” RESTful API should be fully self-describing, such that a client can explore and interact with it knowing nothing but an entrypoint in advance, with hyperlinks providing all necessary context to
24.
by alexpetros 11mo ago
Bonkers but cool! I really appreciate the inclusion of the tree-sitter grammar; I think we should get more used to doing that.
25.
by alexpetros 11mo ago
> Like, you shouldn't be super happy about walking across a desert because your car can't drive on sand. "Look how simple legs are, and they work on sand". I didn't say I was happy about it—I just said I needed t
26.
by alexpetros 11mo ago
I have typically understood the "Sufficiently Smart Compiler" to be one that can arrive at the platonic performance ideal of some procedure, regardless of how the steps in that procedure are actually expressed (as long as they are
27.
by alexpetros 11mo ago
Just fixed it. Nice catch, thank you!
28.
Drupal Ajax is now powered by Htmx(drupal.org)
4 points by alexpetros 1y ago|0 comments
29.
by alexpetros 1y ago
I'd love the article to clarify this, because it stuck out to me as well. But as you pointed out, I think that's what they meant: the lighthouse warning is called "H1UserAgentFontSizeInSection"
30.
by alexpetros 1y ago
Hi, author here. The full quote is: "In my opinion, most websites should be using htmx for either:", and then I list two cases where I think htmx is appropriate. In context, it's clear that I'm not saying "everyone

More ›