freebsd-update-probe VS htmx

https://github.com/tux2bsd/freebsd-update-probe

freebsd-update is broken, it does internal spaghetti which prevents it from doing the most logical thing first: "check upstream for updates"

I created a work around, it works well.

I don't use FreeBSD, but it's good for a hobby OS. Has a few cool ways to do things (seperation of OS vs external software & /etc/rc.conf). The project is coasting on ZFS success.

They HATE me at the FreeBSD Forums. I don't think a single one of them truly understood what freebsd-update-probe actually achieved.

I'm not a programmer.

FreeBSD related shameless plug: https://github.com/tux2bsd/freebsd-update-probe

It makes the update process efficient like it should have been (when there are no updates).

I gave FreeBSD a try:

I provided a workaround for a problem with freebsd-update, summary and tool can found here: https://github.com/tux2bsd/freebsd-update-probe

FreeBSD separation of OS vs other applications is great.

FreeBSD pioneered ZFS integration but are coasting on that success.

The FreeBSD forums, linked from the FreeBSD website are insular. FreeBSD zealots LARPing as the true "true" BSD / Unix enthusiasts.

If you want to try FreeBSD just use the Handbook. The FreeBSD community is childish and won't list that FreeBSD can run on KVM (the mere fact it can, I'm not talking in depth instructions).

I loathe nearly all man pages, they are written in a manner that is as over the top and an absolute chore to digest. I believe it is a form on programmer one-upmanship, it is largely unnecessary and stalls common usage massively.

I made this recently and tried very hard to make it so that the vast majority of people that could use the command line could grasp what it did, usage is trivial:

https://github.com/tux2bsd/freebsd-update-probe

I guess what I'm saying is I like documentation written for humans (which you do).

Recently, I just rewrite one of my application Stashbin from Next.js to GO. Though my main motivation of this migration was to learn GO and experimenting with HTMX. I also aiming to reduce the resource usage of my application and simplify the deployment process. Initially, Stashbin codebase are split into two seperate repository, one for the frontend that uses Next.js and another for the backend that already uses GO. The backend repository is just a REST API responsible for storing and retreiving data from the database.

HTMX is another library that gained popularity due to its server-first approach to rendering data, although seeking a much simpler way of appealing to developers.

When I work with HTMX I need isolated component that can be reusable a form. So I create a PHP Function that generate the Input Datalist.

I was inspired by htmz (which was in turn inspired by htmx) and how the author got pretty close to a basic htmx-like experience just using an iframe. I wanted to push it a little further so whipped this demo together. My submission demonstrates progressive enhancement for the form - with js enabled the request targets an iframe that is inserted into the dom, meaning the page doesn't actually navigate (similar to event.preventDefault()). The iframe receives the html response from the request and on load triggers a function to swap out it's contents into the main page.

As described on htmx.org: "htmx gives you access to AJAX, CSS Transitions, WebSockets and Server Sent Events directly in HTML, using attributes, so you can build modern user interfaces with the simplicity and power of hypertext"

Apart from the source code itself, the repo's README also gives a bit more details about the various packages I used.

1. htmx: https://htmx.org/

Also, there’s some response header juggling you have to do when submitting forms that have a validation step before redirecting: https://github.com/bigskysoftware/htmx/issues/369

I’ve tried to iron out any footguns or server requirements I’ve bumped into while using HTMX & Hotwire in my projects.

✨ In recent months, I have been developing web projects using GOTTHA stack: Go + Templ + Tailwind CSS + htmx + Alpine.js. As soon as I'm ready to talk about all the subtleties and pitfalls, I'll post it on my social networks.

I've been digging into HTMX lately (using Python web frameworks) and find the concepts and approach to be interesting and promising. The idea of hypermedia driven systems over the current practice of JavaScript based frameworks (I never really got into React, played with Vue, and enjoy Svelte/SvelteKit) and the ability to chose your language/framework for the backend while primarily leveraging HTML/CSS on the frontend just seems refreshing.