This site makes a big point of using the term "RESTful" repeatedly, but it seems to be JSON-based by default?

I don't know why modern web frameworks insist on continuing to misuse or misapply the term despite a fairly large amount of messaging recently about how exactly this term is misapplied, and the resurgence of frameworks and tools that do correctly apply it, e.g. HTMX, Datastar, Alpine AJAX.

Otherwise, this looks cool. I'd encourage you to un-roll-your-own docs and use something like Starlight or Docusaurus so you can have usable search and versioned docs.

▲

_heimdall 4 days ago | parent | next [-]

That's a fight we lost two decades ago now unfortunately. Nearly any modern-ish API is a JSON-based RPC. There's nothing wrong with that, JSON RPC is a plenty fine solution for many common use cases, it just isn't REST.

	▲	moritzruth 4 days ago \| parent [-]
		Note that there is also a standard for JSON-based RPC systems, called JSON-RPC [0]. Not every JSON-based self-titled "RESTful" API uses JSON-RPC. [0]: https://www.jsonrpc.org/

▲

elcritch 4 days ago | parent | prev | next [-]

Being RESTful and the data encoding used are largely orthogonal aspects of an API.

Wikipedia RESTful article says:

> The formal REST constraints are as follows:[10]

> Client/Server – Clients are separated from servers by a well-defined interface

> Stateless – A specific client does not consume server storage when the client is "at rest"

> Cache – Responses indicate their own cacheability

> Uniform interface

> Layered system – A client cannot ordinarily tell whether it is connected directly to the end server, or to an intermediary along the way

▲

dustbunny 3 days ago | parent [-]

The key line is actually this:

>An application that adheres to the REST architectural constraints may be informally described as RESTful, although this term is more commonly associated with the design of HTTP-based APIs and what are widely considered best practices regarding the "verbs" (HTTP methods) a resource responds to, while having little to do with REST as originally formulated—and is often even at odds with the concept.

	▲	elcritch 3 days ago \| parent [-]
		Taking that to mean you disagree. However using HTTP verbs has nothing to do with using JSON or not. Notice it says "HTTP" not "HTML" APIs.

▲

4 days ago | parent | prev | next [-]

[deleted]

▲

jadbox 3 days ago | parent | prev | next [-]

What do you think of HTMX vs Datastar for a new production app? Any key reasons to use one over the other?

▲

dustbunny 3 days ago | parent | prev [-]

Ha I came here to complain about the same thing.

Kinda makes me disappointed in the authors especially when they link to the REST wikipedia page as if they know what it means.