Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
alexpetros
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
6 ms
·
31.
▲
by
alexpetros
2y ago
You're right about the quote, thanks for pointing that out. And somehow I can't find the original one anymore, which is frustrating. I replaced it was a different quote from the same guy saying the same thing elsewhere in the disc
32.
▲
by
alexpetros
2y ago
In the near future I'll write a blog about this, but the short answer is that even though more developers use REST incorrectly than not, it's still the term that best communicates our intent to the audience we are trying to reach.
33.
▲
by
alexpetros
2y ago
> 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 infrastr
34.
▲
by
alexpetros
2y ago
In many cases, browsers will also automatically perform a "smooth" transition between pages if your caching settings are don well, as described above. It's called paint holding. [0] One of the driving ideas behind Triptych is
35.
▲
by
alexpetros
2y ago
> The alternative is to have hypermedia for the UI on the one hand, and separately JSON/whatever for the API on the other. But now you have all this code duplication. What code duplication? If both these APIs use the same data fetch
36.
▲
by
alexpetros
2y ago
Co-author here! I'll let the proposal mostly speak for itself but one recurring question it doesn't answer is: "how likely is any of this to happen?" My answer is: I'm pretty optimistic! The people on WHATWG have be
37.
▲
by
alexpetros
2y ago
It sounds like the client you're describing is less capable than the client of 2005, and I'd be curious to hear why you think that's a good thing.
38.
▲
by
alexpetros
2y ago
Hey 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...
39.
▲
by
alexpetros
2y ago
Hey Simon, maintainer + article co-author here. tl;dr htmx is better than a lot of alternatives, but Simon is right, it can improve this story and it has a responsibility to do so. As a framing device: any interactivity that is not describe
40.
▲
by
alexpetros
2y ago
Hey Dan, htmx maintainer here. I would love to know in what other two ways relative links are broken, and which event stopped working, so we can get those fixed. With respect to the fix you PRed (thank you, by the way), we did get that merg
41.
▲
by
alexpetros
2y ago
Anything that can be loaded as a stylesheet or a script tag works great with htmx. These are not htmx-branded libraries... because they're just web libraries.
42.
▲
by
alexpetros
2y ago
I'm sorry to be a little rude, but the AI-generated cover (the left crab is missing an eye, for starters) is a negative quality indicator. If you weren't willing to take the time to put together a thoughtful cover, why should read
43.
▲
by
alexpetros
2y ago
There's a very clear skill ceiling on the kind of code for which LLMs can serve as a productivity multiplier.
44.
▲
by
alexpetros
2y ago
> LLMs will further amplify the existing winner-take-all, first-mover nature of dev tools This will be true for people who rely on LLMs to code , which I strongly suggest is not a great long-term bet for a software engineering career.
45.
▲
by
alexpetros
2y ago
First of all, this is awesome work and it's wonderful to see people taking writing plain HTML seriously, because, as you identified, the existing tooling is completely insufficient. That having been said, I think the reason people larg
46.
▲
by
alexpetros
2y ago
This is not declarative programming, it's codegen. Codegen has its place, but it does not have the most important property of declarative interfaces: that the implementation can improve without altering the code. As others have pointed
47.
▲
by
alexpetros
2y ago
First off, really appreciate you engaging with the feedback so thoughtfully! > This does actually make it pretty robust, although it does become an issue if you actually want to support cross-site form posts. But that is a pretty niche u
48.
▲
by
alexpetros
2y ago
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
49.
▲
Who's Afraid of a Hard Page Load?
(unplannedobsolescence.com)
3 points
by
alexpetros
2y ago
|
0 comments
50.
▲
by
alexpetros
3y ago
I think it's a little more accurate to say that htmx lets you handle the common cases with client-side attributes , so that you only have to bust out the client-side scripting in rarer cases. You're definitely correct that the
51.
▲
by
alexpetros
3y ago
Hah that's amazing
52.
▲
by
alexpetros
3y ago
"Just a few attributes and we could avoid the iframe" could be the htmx/z motto
53.
▲
Web Security Basics (With Htmx)
(htmx.org)
7 points
by
alexpetros
3y ago
|
0 comments
54.
▲
by
alexpetros
3y ago
I somewhat agree with you but I think it's important to clarify whether you're talking about htmx or the hx-trigger syntax specifically. In the parent comment you say: > However, I think there's a pretty significant langua
55.
▲
by
alexpetros
3y ago
This is correct, but... logic belongs in attribute strings! Even in basic HTML, it can change what kind of HTTP request your <form> makes, or what kind of value your <input> sends, or where your <a> link goes. Without ques
56.
▲
by
alexpetros
3y ago
Some have called this the "Team of Rivals" approach to open source maintenance.
57.
▲
by
alexpetros
3y ago
The main point I'm trying to make here is that even if you're in the "leap of faith" category, you still on some level have to understand the framework constructs (i.e. its API) in order to make use of it. If that API ch
58.
▲
by
alexpetros
3y ago
I am always perplexed by how many people deny the reality of this. Upgrading TypeScript major versions for any package of non-trivial size and dependencies is often (not always, but often) quite difficult! I wrote about that in my last htmx
59.
▲
by
alexpetros
3y ago
Author here. Happy to admit that bash + jq backends are an excellent reason to use JSON formatted bodies. Godspeed you crazy animal.
60.
▲
by
alexpetros
3y ago
Broadly speaking, that's basically what this article says!
More ›