I have been building frameworks and SDKs for 15 years. From game engines in C++, native SDKs for iOS, creator of Gin Web Framework in Go, core team at Ionic Framework, co-creator of StencilJS and lately working at Builder.io building Qwik, the next gen of resumable frameworks.
It seems like every day there is a new frontend framework released. But do they solve the problems that teams are facing on a daily basis?
Join this debate to learn the pros and cons of hydration, resumability, streaming and more to uncover the benefits and drawbacks of different frameworks and help you decide where to focus next.
Frontend frameworks, and SPA's in general, trade great DX against poor UX in terms of loading time and performance. But as frontends scaled, the DX benefits also suffered because, as a monolith, it became difficult to isolate sections of the code to enable teams to work in parallel without impacting each other.
The new generation of frontend frameworks solve this problem by using a fundamentally new paradigm called Resumability and leveraging HTML, blending the lines between SPA and MPA
1. Current frameworks scale linearly, future is constant.
2. Business can deliver massive amounts of interactivity without hurting performance
3. Developers can focus on authoring component without worrying about the performance
4. Microfrontends becomes trivial, allowing multiple apps to be deployed and build independently.
5. Partial hydration of React and other frameworks
This paradigm shift aims to build extremely complex applications that scale without performance degradation and negative trade offs of developer experience, this is part of our mission at Builder, where we want to allow businesses to ship fast, extremely complex and performant sites.