Комментарии:
Do you use component frameworks?
Ответитьtailwind all the way
ОтветитьQuasar is great. I highly recommend it. I used Vuetify before that but I prefer Quasar after having used both for over a year each.
ОтветитьVuetify also has a treeshaking functionnality, which can be activated automatically. So this an argument to remove from being opposite with Qasar. About integration with mobile, it is also possible with vuetify, you only need to install the dependancy Cordova or Capacitor, which is not a hassle by itself. I am not sponsored in any way by Vuetify, I am here just to illustrate that some 'major differences' between frameworks might not be as huge as some web articles might say (probably sponsored by the way). Your video is great by the way. Thanks Erik!
ОтветитьI had to use it differently depending on the trends of the development project and the technical type of the members.
I personally like the customizability of Primevue.
However, in projects with a small number of front engineers, the coding speed is significantly reduced.
So in such cases, vuetify or quasar are the best candidates.
Unfortunately, vuetify3 is not yet fully compatible with Vue3, so I am in two minds about updating my Vue2 project.
We use Quasar. (About 50,000 monthly active users, of the web app)
ОтветитьQuasar is my favorite.
Work for most cases.
Quick to deliver a product.
I am surprized you didn't mention how much component libraries can complicate the build process. They can make build times much slower (or alternatively make page loads slower, depending on how you ingest your component library). I have a couple projects that my team refuses to update, because we used an old component library and it would be too much effort to figure out how to update the build chain in a way to use newer component libraries, without sacrificing page load times. (we have one project using Vuetify 2 and one using an ancient version of Bootstrap)
ОтветитьVuetify for me, the data tables are awesome and necessary for me
ОтветитьSo ultimately which one would you go with? Of the ones you mentioned it seemed like quasar was the safest choice given maturity.
Ответить..so this is actually a video about AmplifyUI...
ОтветитьI went from vuetify to quasar, and for now it's no regrets, lighter, more responsive. may be a little less aesthetic, but for management applications it is not the most important
ОтветитьQuasar is the best Vue Component Library out there !
Ответитьquasar ftw. lost all hope to vuetify
ОтветитьPrimeVue
ОтветитьThe accessibility is my main reason for using component libraries, with best practices being in second place. These are two things that I'm either not good at or haven't worked on. I know for a fact that I don't think the same way most other people do.
ОтветитьAfter working with React MUI, Vuetify, Blazor, MudBlazor and eversince I worked in Quasar I never went with anything else.
ОтветитьAt my work we built a couple internal component "libraries". Basically atomic components that we could use across our project and just replace the CSS or adapt Tailwind Classes for styles and small changes to global styles and fonts. That way we can keep the basics link/button styles, paddings/margins with Wrapper/Container components pretty much consistent across the whole site.
Ответитьwhat do you think about unocss? made by antfu
ОтветитьUnoCss + daisyUI
ОтветитьForgot PrimeVue again 🤦🏻♂️
ОтветитьPrimeVue should not be left out ... They've made great improvements in the last 2 months. Through 2021-2022 they were a much better choice for Vue 3 than Vuetify. Quasars tooling has been loaded with bugs and poor quality legacy Node code and a very bad culture that shunned ESM up to 2022, last time I checked.
ОтветитьWhy aren't more people talking about primevue? I'm interested in using it for my next project but there isn't much hype about it and I'm not sure why. I have done projects with vuetify and quasar, and have had great experiences with both, but especially quasar 😊
ОтветитьMy pick was PrimeFaces. (PrimeVue)
Ответитьtailwind + vite/vue or tailwind + nuxt for bigger projects. Have 2 apps in prod running vuetify 2; will be refactoring to remove the dependency on vuetify. Not only it's the crappy material ui, but their release of v3 took forever.
ОтветитьQuasar is the best vue framework I've ever used.
Ответитьafter learning react js, I'm back at Nuxt3 js and I'm 100% going to use vuetify version 3 for my 2 projects.
I'm so thrilled cause of it.
thank you erik for making such great contents around vuejs.
I have learned a ton so far. so thank you again for being a great mentor.
I understand that this clarifies a lot about the pros and cons. I am fairly new to programming and Vue at the moment, and I am having a hard time deciding what to use. I have just finished a basic Vue tutorial and now feel overwhelmed by the wide range of possibilities. My main goal is to create an application that works on both tablets and PCs. It will be for a sports team where I can create profiles and keep track of their performance. I would like to display the records in a dashboard-style format.
Initially, I was almost convinced that I should use Vitesse (which uses UnoCSS, similar to Tailwind, I believe), as you mentioned in another video. However, I am now considering whether Quasar or Vuetify would be better options.
Any help you can provide would be greatly appreciated.
Quasar + Vite + UnoCSS = ❤
ОтветитьAmplify doesn't have UI components for Vue except Authenticator
ОтветитьWith a component framework...
Good news: Your app will have a well designed consistent UI.
Bad news: Your app will look just like a thousand other apps.
If you do all your own CSS and components...
Good news: Your app will have exactly the UI that you want.
Bad news: Everybody else will think your app is weird and fugly.
Last time I tried Vuetify the docs were so horrible that even though I spent 4 days building my site with it, I decided to rewrite everything.
Ответитьhear me out: Tailwind + Quasar = ♥
ОтветитьThanks for this vid !
Gonna be a great help for a lot of devs, even "seniors" ...