“Wow… that’s a big statement… really Shai? is this.. “the Future”?”
“How can a technology which is still in Beta be considered the next big web development framework?”
Well… based on my experience, the research I’ve done and the thorough analysis of the past 26 years of web development and the patterns that emerged along the way… All signs show that we’re at the beginning of a new generation of web frameworks.. and based on how this future will look like, Qwik is years ahead in making it a reality now.
The change is coming, it’s inevitable and it has already begun!
Luckily for us web devs it comes with lots of cool and exciting new technology innovations and opportunities reserved for early adopters.
So what are the patterns I discovered that no one else is talking about? What will be the mainstream way to develop web apps in the future? Why did I decide to put my chips on Qwik as the right investment to make?
All of that and more will be revealed in this talk.
Building instant-on web applications at scale have been elusive. Real-world sites need tracking, analytics, and complex user interfaces and interactions. We always start with the best intentions but end up with a less-than-ideal site.
Let's look into the anatomy of a slow site and dissect it to find out how each issue got there and why fixing it is not a trivial exercise. Understanding the problem is the first step. Next is to think about possible solutions to prevent this.
- Anatomy of a slow site
- Understanding the PageSpeed budget
- Third-party code
- First-party code
- Hydration problem => front load JS
- Lazy loading problem => can't lazy-load visible components
- Resumability is a possible solution => but it is hard