0:00 Intro 1:00 Conversation starts 1:23 Tiered architectures 5:40 Why now? (Edge compute) 8:00 Innovations in compilers 10:05 HTTP becoming the dominant protocol 13:05 Opinionated patterns 14:45 Where does the data live? 18:15 What happens when you start merging content? 19:37 Vercel Edge config (private beta) 20:35 "Data containers" 21:23 Security - Where do you put the credentials? 23:56 Developer productivity 29:54 Long term evolution of JS inside & outside browser 32:16 Will Vercel build something for data? 37:25 Cache invalidation at the edge 43:41 Debugging at the edge 49:03 Developer shortage 54:15 Security and granularity at the edge 59:43 Server-side & client-side responsibilities 1:08:05 Handling leaky abstractions 1:15:15 What are Vercel & Next.js doing with open-source? 1:19:27 A/B Testing & Experimentation 1:21:54 Wrapping up: What's next in Next.js?
Love the discussion about the developer shortage and "what is a developer?" (starting at 48:58). I think we need to talk about these things more. We're all just trying to solve problems and make cool stuff-let's not get too bogged down in how, and which ways are "real" development.
"Developer shortage". More like "the third world isn't exactly sending us our brightest". This "shortage" is what you get when you place preference on foreigners above your own citizens.
What part of this is opensource / cross vendor sourceable? I got the broad sense of the idea being discussed, and it looks like an idea whose time has come. But for it to become the new way of building applications, it has to be a standard or at least an architectural pattern that can be realized using alternative vendors. Drawing parallels to Kubernetes, I am not locking myself into google cloud by accepting K8S. But this looks like a lock-in.
LOL, if the future even has the capacity to keep the Web going. The US keeps devolving into a third world banana republic that can't even properly its own water an electrical grids, the internet might become a luxury.
Its a shame the questions were so scripted and it wasn't so much of an open discussion. There was some real amazing talent in the audience who had the questions that developers want to know, not this marketing PR stuff
0:00 Intro
1:00 Conversation starts
1:23 Tiered architectures
5:40 Why now? (Edge compute)
8:00 Innovations in compilers
10:05 HTTP becoming the dominant protocol
13:05 Opinionated patterns
14:45 Where does the data live?
18:15 What happens when you start merging content?
19:37 Vercel Edge config (private beta)
20:35 "Data containers"
21:23 Security - Where do you put the credentials?
23:56 Developer productivity
29:54 Long term evolution of JS inside & outside browser
32:16 Will Vercel build something for data?
37:25 Cache invalidation at the edge
43:41 Debugging at the edge
49:03 Developer shortage
54:15 Security and granularity at the edge
59:43 Server-side & client-side responsibilities
1:08:05 Handling leaky abstractions
1:15:15 What are Vercel & Next.js doing with open-source?
1:19:27 A/B Testing & Experimentation
1:21:54 Wrapping up: What's next in Next.js?
Thank you very much! We used these in the description - hope you don't mind.
@@VercelHQ Awesome. I really enjoyed the talk and conference! 🙂
Love the discussion about the developer shortage and "what is a developer?" (starting at 48:58). I think we need to talk about these things more. We're all just trying to solve problems and make cool stuff-let's not get too bogged down in how, and which ways are "real" development.
"Developer shortage". More like "the third world isn't exactly sending us our brightest". This "shortage" is what you get when you place preference on foreigners above your own citizens.
So cool to see these folks chop it up over arguably the most fascinating tech we got 😊
Kelsey's answer to Laura's question needs to be shouted from the rooftops
what a story at 1:02:00! that is a story that the enterprise business folks want to hear!!!
Edit: Video is now edited down, so my timestamp is no longer relevant.
It's looking like Geocities (or angelfire) with tags everywhere! 🤣
What part of this is opensource / cross vendor sourceable? I got the broad sense of the idea being discussed, and it looks like an idea whose time has come. But for it to become the new way of building applications, it has to be a standard or at least an architectural pattern that can be realized using alternative vendors. Drawing parallels to Kubernetes, I am not locking myself into google cloud by accepting K8S. But this looks like a lock-in.
I love this ❤️
LOL, if the future even has the capacity to keep the Web going. The US keeps devolving into a third world banana republic that can't even properly its own water an electrical grids, the internet might become a luxury.
Its a shame the questions were so scripted and it wasn't so much of an open discussion. There was some real amazing talent in the audience who had the questions that developers want to know, not this marketing PR stuff
He has to be an MKBHD sibling
:)