Last time I wrote here was almost 6 years ago: https://honestmusings.wordpress.com. Not sure when I will write again.

The first step counter button is supposed to reload the page. The second step buttons update the page w/o reload

The second counter adds and subtracts values other than 1 and therefore seems broken.

That's because there are hundreds of people coming from hacker news clicking the button. if you just refresh the page you can see the number change. The current total seems to be saved server side

Its locking and the state is shared. Didn’t expect a lot of interest for this or I would have built a better demo :)

htmx is great!

The (claimed) value proposition is leveraging block/template to decompose the html page and bind its computation to browser events over a pubsub channel. Its a toolkit and not a framework so one can still use their favourite framework. The Go library isn’t doing anything earth shattering but re-implementing the aforesaid design would still need to be done in any framework.

The state is shared between users for the demo. Its possible to separate state in the library per user but I haven't enabled it.

It’s a rather confusing demo. If that’s the intended behavior, I think you need to think of a less surprising use of it that can be understood as a demo, and perhaps even comes across as a benefit rather than a bug.

Seems like everyone is just pushing the red button. Let me give some love to green button.

I pressed the green button a bunch. Like, a LOT. Zero is such a nice, healthy, round number.

As a sibling said, this is not a bug, but a feature, if explained as such.

Yeah I was afraid of that. Websockets are costly. Thankfully the approach doesn't completely depend on websockets so I have disabled it for now on the site.

It is intended as a longer-term project originating from the previous experiment: https://github.com/adnaan/gomodest. You are right, a better selection criteria for the target audience should be enlisted. I have been working on this for a while so I just got greedy for some early feedback.

This example has most of the scenarios you have called out: https://github.com/livefir/fir/tree/main/examples/fira. Fir aims to limit itself to rendering templates on the server and making it available for all subscribers as a browser CustomEvent which is consumed by alpine.js for more complex interactivity. The expectation is the that the developer handles it via either alpine.js plugins or standard JS code.

[edit] This is still a work-in-progress so I will certainly add better guides and documentation moving forward. Although its good to get feedback that this approach might be interesting for at least some people.

I think this is adding unnecessary complexity. One of the reasons developers gravitate towards a framework like Alpine or HTMX is to write less JS and go back to enjoying HTML. Of course there are a lot of use cases that require custom JS scripting. But bootstrapping a project with another Go web framework and adding Alpine is also trivial. But keep going and follow your vision. I love these types of projects. Check this one out:

https://pushup.adhoc.dev

It's got some unique ideas.

Hey. I have checked out pushup before. Its great. I guess I am taking a niche approach which not many would find useful. To clarify: What is adding more complexity? alpinejs ?

The app was on a 256mb instance. I have scaled it to 2gb. Let's hope its sufficient for now

An in-situ todo list in every tool I use. In slack: scheduled messages, email: todo folder, git: todo.txt and so on. I no longer fight context switching and focus on getting things done in an organised way every time I switch context to a new task.

To write complex code while I am procrastinating or context switching I have taken to writing in plain english what I want to achieve and then write code. It’s cheaper to get all the bad ideas out in plain english while making reasonable progress.