Just a suggestion, the font for the documentation is too thin and maybe too small

@s-molinari
Thank you for your reply. My decision was made when I read the upgrade documentation.
New projects will be with Vuetify. I have applications in version 0.14 and others in version 0.17 and it is sometimes difficult to switch from one to another. Three versions would be more complicated than learning a new framework.
I think the Vuetify API is more stable.
Why rename ‘plugin’ in ‘boot’? q.i18n to lang ?, tertiary color to accentuate? … and so on.
To avoid confusion, all components should have been renamed, such as QInput to NInput.

@s-molinari
Today, I have to start a new project. I have 3 solutions v0.17 (end of life), v1 (in beta) and vuetify.What is the best solution? I’m very familiar with v0.17 and now I have to learn V1 or Vuetify and I think Vuetify’s API will remain stable.

@rstoenescu
Quasar looks more and more like vuetify. Material Design Component Framework with Vuejs
Give me a good reason to stay with Quasar

Everyone is excited by the new version but for me the API has changed a lot.
I like v0.17. It’s a mature version and I use it for many projects. Why not keep this API in v1 and create a new API for the V2? I’m not sure that V1 is faster than V0.17. All the work is done by vuejs and web browser.
I gave up Angular, bootstrap for this reason and jumped to quasar. And now, I think Quasar is trying to clone Vuetify (look at the documentations).
Need to rewrite all projects again. I don’t want to give up Quasar for Vuetify.
Quasar stays different .

@ben-hayat
There is also good documentation at https://devdocs.io. You can navigate with the keyboard, view offline and it’s very responsive
It would be best to have Quasar available in this centralized documentation.

Marc

In the documentation, the transitions are not very useful. In everyday life I would prefer without

Just a suggestion, the font for the documentation is too thin and maybe too small