3 ms·
anybody remember there was a library that combined htmx + alpinejs as one ?
by deisteve 2y ago
anybody remember there was a library that combined htmx + alpinejs as one ?
- indigodaddy 2y agoAlpine Ajax maybe? https://alpine-ajax.js.org/ https://alpine-ajax.js.org/
- deisteve 2y agothere was actually another library but alpine ajax is close tooo
- indigodaddy 2y agoCool I’d be interested as well then
- moritzwarhier 2y agoI'm not an active user of both (but used Alpine in the past), but this is not what you are seeking, or is it? https://v1.htmx.org/extensions/alpine-morph/ https://v1.htmx.org/extensions/alpine-morph/
- deisteve 2y agoi found it https://data-star.dev/ https://data-star.dev/ never used it curious to know if anybody have https://news.ycombinator.com/item?id=41482052 https://news.ycombinator.com/item?id=41482052
- moritzwarhier 2y agoAh OK, thanks for your reply. Wasn't sure what you meant by "bringing together". I assumed you were meaning to connect both, not replace. Fair though. I'm wondering whether the next big thing in this space is going to be more BE-driven and include streaming larger fragments or some other sort of improvement. Anything that does more than Alpine and htmx so far seems to struggle bringing innovation. It was fun once working on a Laravel project where it was somdtimes confusing for a new collaborator to make sense of which "x-attributes" were Alpine, so client-JS-related and which ones were part of server-side Blade templates, so dynamic but not "reactive". This naming collision was preventable and misleading, but it somehow still "felt right".
- deisteve 2y agoI also think server-rendered reactive apps are the future. Elixir/Pheonix comes to mind but the liveview stuff seems complex for most FE apps which don't require more efficient data diff over the wire. i'd say most FE apps are just fetching stuff from BE via rest api and while i think rpc, tanquery all this stuff hides all that plumbing by blending it, but if you get BE to render it from the get go with all the state is handled on the server you wouldn't need FE devs an entire BE team could create a REACTy application even with existing solutions like inertia.js going back to htmx, this is interesting aspect of morph: <div hx-target="this" hx-ext="alpine-morph" hx-swap="morph"> <div x-data="{ count: 0, replaced: false, message: 'Change me, then press the button!' }"> <input type="text" x-model="message"> <div x-text="count"></div> <button x-bind:style="replaced && {'backgroundColor': '#fecaca'}" x-on:click="replaced = true; count++" hx-get="/swap"> Morph </button> </div> </div> but then in datastar its very straight forward but its doing different things I understand. data-store="{ id: 1, firstName: 'John', lastName: 'Doe', email: 'joe@blow.com' }" gets appended as an attribute to id=contact_1 similar to htmx-morph but this is far more readable and intuitive imho <div id="contact_1"> <label>First Name: John</label> <label>Last Name: Doe</label> <label>Email: joe@blow.com</label> <div> <button data-on-click="$$get('/examples/click_to_edit/contact/1/edit')"> Edit </button> <button data-on-click="$$get('/examples/click_to_edit/contact/1/reset')"> Reset </button> </div> </div> one thing that concerns me about datastar is that its quite new but seems at least its updated weekly although the last release i see is 4 months ago
- imacrayon 2y agoHelp me understand why you need the JSON in these examples…You’re rendering JSON data on the frontend just to transform it into HTML. The HTML is rendered server-side, so you should be able to skip the JSON and embed the data in HTML, right? `<input name="firstName" value="John">`
- lenkite 2y agohttps://unpoly.com/ https://unpoly.com/ ? The name is really hard to remember for some reason.
- JodieBenitez 2y agounpoly is excellent !
- deisteve 2y agoi never got used to it. I want to get into it but im not sure what it is that stops me from using unpoly more
- recursivedoubts 2y agomaybe https://data-star.dev/ https://data-star.dev/?
- deisteve 2y agoyup!