Comparisons
A few comparisons between QGP and popular alternatives.
This is just our opinion! If you like building with something else, that’s great! This page just exists to help you make an informed decision.
Why not just Astro?
Astro is incredible, but developing complex single page applications is not it’s focus. We explain more in our FAQ, but the short version is that Astro has limited Hot Module Reloading (HMR) which is a critical feature for developing modern web apps. Astro is only at 2.0, so perhaps this will improve in the future. But for now, QGP is here to fill that gap.
Why not just Vite?
While Vite is a great tool, it is not a framework. It is a development tool that is designed to be used within the context of a framework. You can easily build something with it that implements server-side rendering with island architecture, but putting all of that together yourself is a lot of work.
Astro is a great example of a framework that uses Vite under the hood, and it solves almost every problem one can imagine— except for HMR. In this regard, it doesn’t get much better than Vite. So, why not put them together? That’s exactly what QGP does.
Why not Create React App?
Create React App (CRA) was revolutionary in 2016. Front-end web tooling had gotten so complex that the entry-point was out of reach for many new developers. CRA made it easy to get started with React, and it was a huge success. But, it has grown outdated and neglected to the point where even the React team has admitted that it should probably no longer be recommended.
There are many reasons for this. In this author’s opinion, here are the top four:
- It is not extendable. It’s difficult to add plugins or modify the webpack config.
- It is not flexible. You can only build client rendered single-page applications.
- It is not performant. It is slow in many ways— HMR, build times, and user experience.
- It is not modern. The opinionated structure was great in 2016, but it isn’t relevant now.
In conclusion, here’s a short video from the popular influencer Theo Browne that explains why he doesn’t think anyone should use CRA or WebPack anymore. He’s not wrong. Apparently, WebPack has been experimenting with a Rust rewrite recently, so it may outlive CRA.
Why not Next.js?
This will not be a slander piece on Vercel. They are a great company and they have done a lot in terms of pushing the web forward. But, Next.js is not for everyone. And, it is currently in the midst of an extreme makeover that is not finished.
While it looks like Server Components will be revolutionary, the app directory has been out for four months as of the writing of this piece, and there is still no mutation API. We can’t wait to see what it eventually becomes, but it’s changing rapidly and it is hard to use in production. In the last month, Astro released 2.0 and Vite released 4.0 with remarkably few breaking changes. QGP is being used in production today.
Any other alternatives?
Remix, SvelteKit, SolidStart— there are a lot of great options out there. QGP is just one. We won’t try to convince you which one is best. Honestly, we think they are all great. We just really love building with Astro, so we made QGP to make it even better. Let us know what you think!