Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Suggestion - Reclassification of Quasar Framework within the State of JavaScript Survey #477

Open
smolinari opened this issue Dec 18, 2024 · 3 comments

Comments

@smolinari
Copy link

smolinari commented Dec 18, 2024

Dear Devographics Team,

I am writing to respectfully suggest a potential reclassification of the Quasar Framework within your valuable State of JavaScript survey. Currently, Quasar is listed under the "Mobile and Desktop" section. While Quasar certainly excels at building hybrid mobile applications (via Capacitor) and Desktop apps (via Electron), its capabilities extend significantly beyond just mobile and desktop development, making it more accurately categorized as a meta-framework.

Quasar offers a comprehensive suite of tools and features that support the development of a wide range of applications from a single code base, including:

Single-Page Applications (SPAs): Quasar provides a robust foundation for building modern web applications with Vue.js.
Progressive Web Apps (PWAs): Quasar has first-class PWA support, simplifying their creation.
Server-Side Rendered (SSR) Applications: Quasar allows for building SSR applications, improving SEO and initial load times.
Desktop Applications (with Electron): Quasar facilitates the creation of cross-platform desktop applications.
Mobile Apps (with Cordova/Capacitor): As currently recognized, Quasar supports hybrid mobile app development.
Quasar even helps developers build browser extensions.

Given this breadth of functionality, encompassing web, mobile, desktop, and server-side rendering, classifying Quasar solely within the "Mobile and Desktop" section of the survey seems to underrepresent its full potential and scope. Placing it within the "Meta-Frameworks" section, alongside frameworks like Next.js, Nuxt.js, and SvelteKit, would more accurately reflect its capabilities and its role in the JavaScript ecosystem and provide more relevant data for the survey.

We understand the effort involved in creating and maintaining such a valuable resource, and appreciate your consideration of this suggestion. We believe this reclassification within the survey would provide a clearer picture of Quasar's role and benefits to developers and contribute to more accurate survey results.

Thank you for your time and dedication to the State of JavaScript/HTML/CSS projects.

Sincerely,

Scott Molinari
Quasar Framework Media Manager

@hawkeye64
Copy link

100% agree with this

@SachaG
Copy link
Member

SachaG commented Dec 18, 2024

Are you part of the core team of the project? It would be nice to hear from them too.

That being said I don't think this would benefit the project because its number would not look good compared to e.g. Next.js or Astro.

@smolinari
Copy link
Author

smolinari commented Dec 18, 2024

@SachaG

Are you part of the core team of the project?

Yes.

That being said I don't think this would benefit the project because its number would not look good compared to e.g. Next.js or Astro.

Not looking good isn't a worry for us. It's Quasar being correctly categorized for what it that we would like to get accomplished.

Scott

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants