The choice is simple - Vue. Why? Because it has Quasar.
hipertracker
thiagomajesk
AlpineJs! Because it’s the only framework that makes working with Javascript bearable. It also reminds me dearly of the KnockouJs golden era (where Javascript was only used to sprinkle HTML with magic). Another factor that contributes to my choice is that I prefer to work with SSR / HTML-centric applications.
2
superchris
Thanks for the shout out 
We’ve used LiveView and Web Components together now on several projects and it’s worked out very well. In my humble opinion, it’s a perfect fit. Live View is great at managing DOM Elements, and since Custom Elements are still just DOM Elements at the end of the day, it makes a nice boundary to add in javascript when it is the best solution to a specific problem.
8
amnu3387
In the context of pure web apps (can’t speak for needing native) when able to choose and pre-liveview I would go Nuxt/Vuejs2.
React also seems to work fine.
If I had time I would like to try Svelte & Elm. I wouldn’t choose Angular ever.
It’s funny that from those (except svelte & elm that I haven’t tried), only Vuejs doesn’t natively support TS (or didn’t), and still it’s way easier to build correct, fast, complex applications with it, while the others when using TS I can never be sure they’re correct. I haven’t used Vuejs3 so can’t speak about it, but was a bit sad to see the push towards hook-like flows as I (for reactive UI’s) prefer quite a bit the original Vue organisation and declaration style.
Now I think I will use predominantly LiveView with a bit of plain JS (Alpine works fine but I prefer to not use another dep if I can get away with it). Testing and capabilities are simply unmatched and most of the problems I ran into were easily solved or simply required a different approach to how they would be done in a SPA.
0
Brainiac
Using Liveview Components with React works great. This allows react to handle all the presentational aspects, which include transitions, ui kits and allows leveraging oftthe JS ecosystem. While all state is held by the liveview process, eliminating the need for redux, routing, etc. Its quite easy to control components server side as well, or swap out react components on the fly.
6
cnck1387
I really like https://stimulus.hotwired.dev/. IMO it’s a really good balance between decorating your HTML with a few attributes to handle basic configuration and bindings while the core logic of what your JS does lives is its own isolated JS file which makes it super easy to reuse things without duplicating a ton of code.
It was created by the Rails team so it comes with a number of conventions out of the box to reduce boilerplate in general. I haven’t found another front-end library that makes it so easy to integrate and reuse common functionality not only in the same project but across different projects too.
As someone who isn’t big into JS and being brand new to Stimulus, it was pretty easy to get going. It took about a day to get generic reusable Stimulus controllers for things like a color picker preview, ajax content loader, image upload preview, file upload validation, toggling visibility, tabs and modals.
No extra external libraries were used to get the above functionality too. Most of those controllers are 15-50 lines of super straight forward JS. Stimulus really sets up nice abstractions to ease you into developing real world features.
6
kgllev
egeersoz
I have a Vue app with over 70k lines of code. It has scaled very well since the beginning and has allowed me to be productive. Unlike React, I feel that Vue gives you a lot of freedom and flexibility, and does not get in the way.
I use Vuetify as the material design framework. It’s the largest UI framework in the Vue ecosystem I believe, and has a large team behind it and receives regular (weekly) updates.
1