From 9a4483ea83608a5e7b32b891f4d35f515f80c9bf Mon Sep 17 00:00:00 2001 From: Carson Gross Date: Sun, 5 Jan 2025 09:43:52 -0700 Subject: [PATCH] add copy & paste components as a Con for htmx --- www/content/essays/when-to-use-hypermedia.md | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/www/content/essays/when-to-use-hypermedia.md b/www/content/essays/when-to-use-hypermedia.md index 7436b964..9f41f397 100644 --- a/www/content/essays/when-to-use-hypermedia.md +++ b/www/content/essays/when-to-use-hypermedia.md @@ -174,6 +174,15 @@ architecture, than vice-versa. Isolated client-side components can communicate via [events](https://developer.mozilla.org/en-US/docs/Learn/JavaScript/Building_blocks/Events), in the manner demonstrated in the [drag-and-drop Sortable.js + htmx](@/examples/sortable.md) example. +### _...If you want integrated copy & paste components_ + +Recently we have seen the rise of "Copy & Paste" friendly components such as [ShadCN](https://ui.shadcn.com/). +These components are typically designed for a specific front end framework such as React, and choosing htmx means that +you can't use them. + +There are front-end library neutral component libraries such as [lit](https://lit.dev/), but they are not as integrated +with htmx as ShadCN is with React. + ### _...If your team is not on board_ A final reason to not choose hypermedia isn't technical, but rather sociological: currently, hypermedia simply isn't