Live data from Hacker News

Show HN: Build progressively enhanced reactive HTML apps using Go and Alpine.js

livefir.fly.dev

11–20 of 45 posts

Re: Show HN: Build progressively enhanced reactive HTML apps using Go and Alpine.js

#14

The second example counter is jumping around instead of incrementing/decrementing by 1. Is state being shared between users or somesuch? Or is it because I first clicked the full reload example several times? iOS

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.

Re: Show HN: Build progressively enhanced reactive HTML apps using Go and Alpine.js

#15
I'm building a platform using GoFiber + AlpineJS and it's wonderful. I have to go through the Fir project because I'm trying to figure out what problem it solves. Wouldn't it be just as easy as using the vanilla net library + Alpine or one of the more established Go frameworks + Alpine? Honest question. If Fir has a value proposition that's unique im still in a position to pivot.

Re: Show HN: Build progressively enhanced reactive HTML apps using Go and Alpine.js

#17
post #3

The idea of using Go and Alpine.js together for building reactive web apps seems promising. As you mentioned, Fir is targeting devs with moderate HTML/CSS & JS skills. How does Fir handle more complex scenarios such as nested components, handling form submissions with client-side validation, and integrating third-party APIs or libraries? Does the toolkit offer any built-in functionality or guidelines for handling the…

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]…

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.

Re: Show HN: Build progressively enhanced reactive HTML apps using Go and Alpine.js

#18
post #15

I'm building a platform using GoFiber + AlpineJS and it's wonderful. I have to go through the Fir project because I'm trying to figure out what problem it solves. Wouldn't it be just as easy as using the vanilla net library + Alpine or one of the more established Go frameworks + Alpine? Honest question. If Fir has a value proposition that's unique im still in a position to pivot.

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.

Re: Show HN: Build progressively enhanced reactive HTML apps using Go and Alpine.js

#19

I wonder if it slow because of the locking, because other than that it shouldn't use much resources to run this. Anyway I am lazy, so I would probably just use HTMX boosting: // traditional code goes here

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!

Re: Show HN: Build progressively enhanced reactive HTML apps using Go and Alpine.js

#20
post #17

Earlier quoted context omitted.

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]…

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…

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 ?
Post reply on HN