It's true that in the demo video, it's only called out that a third party dependency was removed from the client bundle. And it's true that these types of "infra" dependencies don't make up a large % of your codebase to begin with.
But there's another angle to consider. In thick client apps, product code (everything else) tends to take up the majority of the size of the client bundle. There's a real opportunity here to move some of that into Server Components which would help reduce that footprint significantly. For example consider the case of deeply wrapped components that ultimately render to a single <div>. Server Components could help remove that abstraction tax.
Netflix | Senior Frontend Engineer | Los Gatos, CA | ONSITE, FULL TIME | We pay top of market
How do you spark joy in hundreds of millions of people? It starts with a vision—that technology can give voice to stories around the world. Netflix empowers a small band of creatives to do what no studio has ever done—tell hundreds of stories you fall in love with and stay up watching.
As an engineer on the Studio Engineering team, you’ll help us reinvent the way TV and movies are made on a global scale. If you have an eye for software design, a mind for asking questions and synthesizing information into actionable work, and the personality to want to learn from AND teach your teammates - we would like to talk to you.
Our culture is unique. It's not for everyone, but if it sounds like you, and describes the people you want to work with, you'll thrive at Netflix. https://jobs.netflix.com/culture
Netflix | Senior Software Engineer | Los Gatos, CA | ONSITE, FULL TIME | We pay top of market
How do you spark joy in hundreds of millions of people? It starts with a vision—that technology can give voice to stories around the world. Netflix empowers a small band of creatives to do what no studio has ever done—tell hundreds of stories you fall in love with and stay up watching.
As an engineer on the Studio Engineering team, you’ll help us build the future of how Netflix will create and produce shows on a global scale. If you have an eye for software design, a mind for asking questions and synthesizing information into actionable work, and the personality to want to learn from AND teach your teammates - we would like to talk to you.
Our culture is unique. It's not for everyone, but if it sounds like you, and describes the people you want to work with, you'll thrive at Netflix. https://jobs.netflix.com/culture
* Senior Rubyist/Polyglot with experience in building reliable, data-intensive applications in a microservices context - https://jobs.netflix.com/jobs/864653
Reach out to me directly if you have questions - laurent (@) netflix.com
Netflix | Senior Software Engineer | Los Gatos, CA | ONSITE, FULL TIME | We pay top of market
How do you spark joy in hundreds of millions of people? It starts with a vision—that technology can give voice to stories around the world. Netflix empowers a small band of creatives to do what no studio has ever done—tell hundreds of stories you fall in love with and stay up watching.
As an engineer on the Studio Engineering team, you’ll help us build the future of how Netflix will create and produce shows on a global scale. If you have an eye for software design, a mind for asking questions and synthesizing information into actionable work, and the personality to want to learn from AND teach your teammates - we would like to talk to you.
Our culture is unique. It's not for everyone, but if it sounds like you, and describes the people you want to work with,
you'll thrive at Netflix. https://jobs.netflix.com/culture
* Senior Rubyist/Polyglot with experience in building reliable, data-intensive applications in a microservices context - https://jobs.netflix.com/jobs/864653
Reach out to me directly if you have questions - laurent (@) netflix.com
I'd like to make a suggestion for a cool feature: being able to clone someone else's recipe and put my own 'twist' on it. Almost like a git fork, if you want to use that analogy. You could also submit pull requests... you get the idea.
But there's another angle to consider. In thick client apps, product code (everything else) tends to take up the majority of the size of the client bundle. There's a real opportunity here to move some of that into Server Components which would help reduce that footprint significantly. For example consider the case of deeply wrapped components that ultimately render to a single <div>. Server Components could help remove that abstraction tax.