Sebastian Chopin is the co-author of Nuxt.js and has extensive experience using node.js, Backbone.js, and doing server-side rendering.
Classic SSR is when your dynamic HTML pages are created all on the server-side before sending to the client (browser). A classic Single Page Application (SPA) is when your application code is loaded into the front-end and the browser requests the data (often using an API) and generates the dynamic page.
With Universal Application flow, the node server (on the serverside) does the data API request, generates the dynamic page, and sends HTML content back into the browser.
Thus, it’s a good balance between typical SSR and SPA.
It also allows the creation of a better user experience (UX) and has more security improvements.
Sebastian shows a demo in the video where he builds a Universal rendering engine step by step eventually showing how Nuxt tries to simplify things.
Right now nuxt-edge is coming. It has Weppack 4 integration, no more vendors, full control over chunk splitting, Vue Loader 15, ES Modules, CLI improvments, and many other features.
To manage all the Nuxt issues and questions in the community they’re now using nuxtjs.cmty.io. They found that on github it’s hard to sift through questions/bugs/feature requests, so they needed a better way. This is why he helped created cmty.io, a nuxt project that any open source projects can sign up to use.