You highlighted client side fundamentals (though Accessibility wasn't mentioned) which can be sufficient for Generation 2 front-end development.
With Generation 3 (nothing to do with Web3) it is possible that:
"… we are entering the era where frontend development will shift away from the client-side, and lean much more heavily on server-first architectures."
Next.js SSR is still considered a Gen 2 solution. With Gen 3 the server (or edge) is going to be doing more work so the client doesn't have to.
So understanding both sides (and the constraints they operate under) will become increasingly important (Rendering Patterns).
Oh yes, I'm focused on my experience of "styling" things in this article. Thanks for the references by the way.
Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink.
Hide child comments as well
Confirm
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
You highlighted client side fundamentals (though Accessibility wasn't mentioned) which can be sufficient for Generation 2 front-end development.
With Generation 3 (nothing to do with Web3) it is possible that:
"… we are entering the era where frontend development will shift away from the client-side, and lean much more heavily on server-first architectures."
Next.js SSR is still considered a Gen 2 solution. With Gen 3 the server (or edge) is going to be doing more work so the client doesn't have to.
So understanding both sides (and the constraints they operate under) will become increasingly important (Rendering Patterns).
Oh yes, I'm focused on my experience of "styling" things in this article. Thanks for the references by the way.