From fda6dee2200591d16fc9371c94035f3391c6f0df Mon Sep 17 00:00:00 2001 From: Samuel Colvin Date: Fri, 1 Dec 2023 19:43:38 +0000 Subject: [PATCH] pHD -> PhD :sleeping: --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 229c9e0f..12fe2d86 100644 --- a/README.md +++ b/README.md @@ -149,7 +149,7 @@ FastUI already defines the following components, all are shown in the [demo app] ## The Principle (long version) -FastUI is an implementation of the RESTful principle; but not as it's usually understood, instead I mean the principle defined in the original [pHD dissertation](https://ics.uci.edu/~fielding/pubs/dissertation/rest_arch_style.htm) by Roy Fielding, and excellently summarised in [this essay on htmx.org](https://htmx.org/essays/how-did-rest-come-to-mean-the-opposite-of-rest/) (HTMX people, I'm sorry to use your article to promote React which I know you despise 🙏). +FastUI is an implementation of the RESTful principle; but not as it's usually understood, instead I mean the principle defined in the original [PhD dissertation](https://ics.uci.edu/~fielding/pubs/dissertation/rest_arch_style.htm) by Roy Fielding, and excellently summarised in [this essay on htmx.org](https://htmx.org/essays/how-did-rest-come-to-mean-the-opposite-of-rest/) (HTMX people, I'm sorry to use your article to promote React which I know you despise 🙏). The RESTful principle as described in the HTMX article is that the frontend doesn't need to (and shouldn't) know anything about the application your building. Instead, it should just provide all the components you need to construct the interface, the backend can then tell the frontend what to do.