3 ms·
fair point https://harcstack.org https://harcstack.org was used to built the new site in the spirit of use your own dogfood (other raku web modules are availab
by librasteve 1y ago
fair point
https://harcstack.org https://harcstack.org was used to built the new site in the spirit of use your own dogfood (other raku web modules are available)
HARC stack is centred on HTMX (thus the 'H') and Pico CSS (other CSS libs coming)
This version of HARC Stack implements the HATEOS version of tabs https://htmx.org/examples/tabs-hateoas/ https://htmx.org/examples/tabs-hateoas/ since that allows for dynamic content service (but admittedly that is overkill for the current site)
- odie5533 1y agoWow! The Tabs example on the HTMX is faked! They serve the tabbed content using faked JS calls instead of network calls. It makes the idea of using HTTP for small amounts of content changes not seem crazy because it's instant on their site, but when you implement it on your site it will be slow because it's making actual HTTP calls! HATEOS is okay for APIs. But doesn't seem useful for small static sites. Dogfooding is great! But so is using the right tool for the job. HTMX is not over-engineering things, it's made the Raku site worse than plain HTML and CSS (you can do tabbed content in pure CSS even!)
- librasteve 1y agoI respectfully disagree that HTMX (or AJAX) is a bad choice for tabs in general. The classic idea of getting incremental content from the server is important. These HARC stack tabs will work fine if you have eg a set of editable boxes or live timers to present. Following your logic no one would ever reach for React.