Re:Htmx and Web Components: A Perfect Match
by k__ on Thursday January 18, 2024 @08:44AM
(#39041581)
Didn't GraphQL solve this issue already anyway?
[ Parent
| on HN ]
Re:Htmx and Web Components: A Perfect Match
by fl0ki on Thursday January 18, 2024 @11:56AM
(#39044164)
How? GraphQL is just another way to make query API with structured output, almost always JSON in practice. If you wanted server-side rendering, you still need another endpoint even if it happens to use GraphQL internally, just like you could made a rendered endpoint using another form of API internally.
Re:Htmx and Web Components: A Perfect Match
by b33j0r on Thursday January 18, 2024 @02:33PM
(#39046470)
Have you implemented it? The orm aspect is actually pretty weak. You end up implementing an RPC api anyway. And then you wonder how this was sold to you as declarative and idempotent.
I exaggerate here because graphql does not solve the datalake problem. And it doesn’t do graphs (you can). The curb appeal looked super promising, but then it was just rpc with a bespoke ORM syntax.