alpine

This seems to be the reason https://github.com/alpinejs/alpine/discussions/1423

After hesitating with Tailwind I did come around to loving it, but I've had a much harder time getting over my initial impressions of Alpine. I recognize that one, it targets a very specific type of website, and two, it's easy to let subjective feelings about what makes for readable & maintainable code get in the way of an unbiased take on the framework. But writing JavaScript in strings is unappealing to me, even for server-side sites that just need some sprinkling. Some questions that come to mind that would sway me one way or another: - How is the tooling and debugging experience? - Do you get intellisense with the VSCode extension within x-for, x-show, etc. expressions? - Can you easily set breakpoints in devtools and step through your code? - In reference to the issue below, how susceptible would I be to XSS attacks in using this fra

Good point. It's a small JS framework that you might think of as a VueJS/React "lite" https://github.com/alpinejs/alpine

The LiveView is just a HTML page so you can have whatever CSS/JavaScript you like on the client side for animations and interactivity. Talking to the server is opt-in and you’d basically do it wherever you’d usually make an API call from React etc. The go-to for JS in LiveView seems to be Alpine (https://github.com/alpinejs/alpine) but I haven’t got around to trying that out myself yet.

Neat, appears to occupy a similar niche as Alpine: https://github.com/alpinejs/alpine

Fav thread ever! A good 5+ years ago I built HasGluten [1] with react backed by a google spreadsheet, hosted on github pages. Proven technology, it's still working. More recently I hacked together MultiPreview [2] with react + API served by firebase functions. I'm also temp using firebase hosting as I have little traffic, but plan to replace it with edge computing / CDN caching. MultiPreview is backed by Saasform [3]. This is more like a classic node/express (nestjs) application, but I really like how we're separating concerns: the SaaS = MultiPreview handles the biz logic / Saasform handles landing page + auth + payments. While building the new landing page I played with and liked a lot Bulma [4], I used but didn't like AlpineJS [5] and I'm thinking to move to Hotwire [6]. My personal experience is that performance only matters when you'

> Vue can be used just like jQuery without any nodejs tooling You can, but you probably shouldn’t (outside of prototyping). It requires you to both ship the template compiler to the client, and to perform the template compilation on the client, on every single page load (vs serving a cached, pre-compiled JS file). If you want to sprinkle JS onto an otherwise server rendered page, you’re better off with something like Alpine.js [1] [1] https://github.com/alpinejs/alpine

"Alpine.js offers you the reactive and declarative nature of big frameworks like Vue or React at a much lower cost. You get to keep your DOM, and sprinkle in behavior as you see fit... Alpine doesn't use a virtual DOM. This implementation allows Alpine to stay rugged and use the real DOM to work its magic" https://github.com/alpinejs/alpine

This might be interesting to you: https://github.com/alpinejs/alpine/

For the record - here they are alpine.js (https://github.com/alpinejs/alpine) and synergy.js (https://github.com/defx/synergy) repos.