Been using Alpine.js in a Ruby on Rails app for about 6 months now. It's a very cool, lightweight js library that I rarely see talked about.
Show HN: Build progressively enhanced reactive HTML apps using Go and Alpine.js
21–30 of 45 posts
Re: Show HN: Build progressively enhanced reactive HTML apps using Go and Alpine.js
#22I'm currently working with Alpine.js in order to try to build "Universal Components" or "Hypermedia Components". Where you just hit a URL and get your component like /components/infinite-canvas or /components/svg-2-base64 or /components/lib-somelib.
[1] ilse.ink/components(It's not ready yet)
Re: Show HN: Build progressively enhanced reactive HTML apps using Go and Alpine.js
#23I 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
Is there a tl;dr on why I’d want to boost? Vs say normal browser behaviour
Re: Show HN: Build progressively enhanced reactive HTML apps using Go and Alpine.js
#24The 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.
Seems like everyone is just pushing the red button. Let me give some love to green button.
Re: Show HN: Build progressively enhanced reactive HTML apps using Go and Alpine.js
#25Counter doesn't work properly on Android Chrome FYI just reloads the page.
Re: Show HN: Build progressively enhanced reactive HTML apps using Go and Alpine.js
#26Earlier quoted context omitted.
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.
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.
Re: Show HN: Build progressively enhanced reactive HTML apps using Go and Alpine.js
#27The 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.
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.
Re: Show HN: Build progressively enhanced reactive HTML apps using Go and Alpine.js
#28Counter doesn't work properly on Android Chrome FYI just reloads the page.
The first step counter button is supposed to reload the page. The second step buttons update the page w/o reload
Re: Show HN: Build progressively enhanced reactive HTML apps using Go and Alpine.js
#29I 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
Is there a tl;dr on why I’d want to boost? Vs say normal browser behaviour
So that the things that change only appear to update, not a flash of the entire screen. If the request is slow, this makes a bigger difference of course.
Re: Show HN: Build progressively enhanced reactive HTML apps using Go and Alpine.js
#30I'm on Arc (Chromium) and pressing any of the buttons in the first example jumps to the top of the page.