GR: Most JS developers are familiar with AMP -- the technology that Google invented four or so years ago. Sites that have AMP implemented have a lightning icon on search results on Google, and it basically tells users that it's been pre-loaded and pre-rendered by Google. And when you use AMP as a user, the site feels instant, in a way that no normal site feels. AMP has really taken off, as developers want to do whatever they can to secure optimal placement in search results and experience on Google.
It's all related to how the web stays very open, how sites and apps stay very ergonomic by requiring no downloads, but perform as well as native apps.
GR: The general pitch for web frameworks is that when developers are maintaining their own tooling -- configurations, build pipelines, etc -- they tend to quickly fall behind on important optimizations they can make as the web evolves.
By using web frameworks like Next.js, their applications are production ready without doing any of the work. The ecosystem of web browsers is very fragmented, and Next.js gives you the peace of mind that at build-time we handle all these performance optimization to handle varied devices and browsers. Build once, ship everywhere.
BN: Is the experience of being a front-end developer changing with all of these new frameworks?
GR: Absolutely. You were doing a lot of stuff in the past that today is handled by the framework, so you can focus more on just building your site or app.