Yesterday I with help from the clanker, as an experiment, ported a web app from go+postgres+svelte to ari+duckdb+htmx served locally by busybox httpd. Itโs an analytics โdashboardโ so the stack makes sense. So far looks good. Now I work on the code in vim to make it mine. I want fewer layers of abstraction and less complexity, and this is a learning experience to that end.
Any conversation
Ikea has rules for naming products (so in theory, you could figure out what it is from the name) -> www.ikea.com/โฆ/6f564c4d-2ccc-46de-โฆ545a3948dc79.html
signals. thinking about shifting my mental framework to identify signals instead of waiting for concepts to be assembled. exploring the amount of energy and opportunities for distractions through the operations of processing what just happened and what is happening to short circuit latent and unnecessary systems. cut through the assembly processes and identify the raw signals. recognizing that naming these "raw signals" is misleading. maybe, shifting observability lower in the stack.
Having spent the last 12 months using HTMX in $day_job, after 5 years with react, I have come to the opinion that whilst large amounts of JS and CSS are not necessarily wrong, they should be reserved for progressively extending the platform with a composable set of generic UI primitives that build out a cohesive design language โ encoding business logic (including routing) there is generally a mistake




