@aiupjulian
Nothing here yet.
Nothing here yet.
No blogs yet.
I can't remember the URL, but the most incredible CV I saw was with animations, you controlled a guy that walked while telling all his knowledge. It was really impressive. I think that those kind of sites shows little about what can a dev do. You can lie about what you know (and I saw lots of CV that I'm certain they're lying), and you can't have a big site just to tell what you know, you can't use React or Angular, you just need a static page.
From here The most common use case for server-side rendering is to handle the initial render when a user (or search engine crawler) first requests our app. When the server receives the request, it renders the required component(s) into an HTML string, and then sends it as a response to the client. From that point on, the client takes over rendering duties. We will use React in the examples below, but the same techniques can be used with other view frameworks that can render on the server.
From MSDN: " Single - Page Applications (SPAs) are Web apps that load a single HTML page and dynamically update that page as the user interacts with the app . SPAs use AJAX and HTML5 to create fluid and responsive Web apps , without constant page reloads. However, this means much of the work happens on the client side, in JavaScript."
From what I know, React is a client-side framework, and all the work is done by the client (all the code is in the client). That's why they're called a Single Page Application (SPA), all the logic is in the client and always calculates what to render.