Live data from Hacker News

Viewing profile — alexpetros

alexpetros

HN member
Joined
Wed, Apr 20, 2022, 6:14 PM UTC
HN karma
428
Public activity
86 items

About alexpetros

No profile information was provided.

Recent public activity

  1. comment
    Comment #49093487

    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 i…

  2. comment
    Comment #49093449

    > 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 t…

  3. comment
    Comment #49093278

    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 fun…

  4. comment
    Comment #49093249

    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 cur…

  5. comment
    Comment #49093195

    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 …

  6. comment
    Comment #49093185

    > 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 …

  7. comment
    Comment #49093152

    > 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 beca…

  8. story
  9. comment
    Comment #48173986

    Thank you!

  10. comment
    Comment #48173977

    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. comment
    Comment #47378761

    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 choi…

  12. comment
    Comment #47377064

    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 branc…

  13. comment
    Comment #47376943

    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 fro…

  14. comment
    Comment #47376897

    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…

  15. comment
    Comment #47376743

    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, b…

  16. comment
    Comment #45806038

    So here's the htmx example for click to edit: [0] And here's the datastar one, edited for parity: [1] The htmx one is simpler. There's fewer mini-languages to learn and the API mak…

  17. comment
    Comment #45805960

    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 th…

  18. comment
    Comment #45805649

    > 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 …

  19. comment
    Comment #45805126

    > 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 ar…

  20. comment
    Comment #45701560

    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 specif…

  21. comment
    Comment #45701548

    > 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…

  22. comment
    Comment #45701525

    > 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 …

  23. comment
    Comment #45701221

    > 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 adv…

  24. comment
    Comment #45632036

    Bonkers but cool! I really appreciate the inclusion of the tree-sitter grammar; I think we should get more used to doing that.

  25. comment
    Comment #45632030

    > 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…