React VS Alpine.js

A later evolution of this stack was the MERN stack that exchanged React with AngularJS as the frontend web framework.

According to the docs, NextUI is a React UI library that allows you to make beautiful, modern, and fast websites/applications regardless of your design experience. It is created with React and Stitches, based on React Aria, and inspired by Vuesax.

Seeing as reactjs is one of the most widely used JavaScript frameworks for front-end web development, having a whole community of React devs to rely on for questions is always good. And reactiflux fits that bill perfectly.

To understand each framework’s weaknesses and strengths, it is helpful to be aware of where they stem from. After all, like anything else in life, both the Vue framework and React framework have been influenced by their cultural contexts – while React was created by Facebook, Vue was developed by a former engineer at Google.

React is the JS framework that Facebook is using under the hood, and right now is probably the most abundant work out there. This is "front-end" framework which means it primarily deals with the presentation of the app and user interaction.

React The frontend part

1-) React itself react

First I wanted to update my tools, maybe I just needed a small patch instead of changing them. So I made a project for a client using Laravel, Inertia.js Svelte, and then other project using Laravel, Inertia and React. I liked Svelte over React, so if future frontend projects appear, my main tool would be Svelte.

Should check out htmx and alpinejs. Much cleaner if you're not going full SPA. jQuery quickly turns into a spaghetti mess.

I render everything on the server with Go templates and use AlpineJS to sprinkle interactivity.

Basic JavaScript and Alpine.js knowledge

Lately A LOT of AlpineJS. I usually just need simple reactivity as most of what I develop is PHP SSR. This lets me add simple inline reactivity or reusable components pretty easily and quickly.

“petite-vue is indeed intended to fill the gap for progressive enhancement cases where Vue 3 would be too heavy-handed.

It is not abandoned, but rather it is considered "done" because the scope is well defined. I don't think it needs more features (as that would defeat the purpose of being lean and minimal). If you find yourself needing more than what petite-vue provides, you can either go up to Vue proper, or try https://alpinejs.dev/.

That said, I should update the README to indicate this more clearly.”

Github discussion: https://github.com/vuejs/petite-vue/discussions/53

Yeah, this is the dealbreaker for me with alpine.js and htmx.

And I wouldn't even say "tight CSP" as much as "standard CSP." To make alpine.js play nice with CSP, you have to allow unsafe-eval, which severely weakens your protection against XSS.

alpine.js claims to have a compatibility build with CSP, but it's not officially available, doesn't fully work, and the parts that are broken in the CSP build aren't documented.[0]

htmx works under CSP, but it opens a new vector for attackers to inject JS into your page, which effectively neuters CSP.[1]

[0] https://github.com/alpinejs/alpine/discussions/1944

[1] https://htmx.org/docs/#security

> https://htmx.org

I love htmlx. That you so much for this. I'm currently using https://alpinejs.dev/ because it allows me to work directly with HTML so I can have meta-programming capabilities that React.js/Vue.js simply could not handle.

That you for htmlx!

Alpine JS

Pretty much just AlpineJS. Sometimes a Temporal polyfill as well. I work mostly with PHP SSR though.