It was the "right" way for the longest time, because you had a separate graph of changes made to the structure. This graph could be compared with the existing DOM, and this meant that only the thing that changed was updated. This is exponentially better than refreshing the whole page, and it's similar to AJAX updates but "faster" because it doesn't travel back to the server for information. Despite all this good stuff, React still traverses the whole virtual DOM for every single update (even if it's just to increment a count), and all this work is made client-side. You can imagine this is not very efficient. Svelte fixes this problem, among others.

Me too

That's not a stupid question at all! In fact, it's an important question that many people may have. When it comes to web development, there are different ways to approach building and shipping code. In general, there are two main approaches: server-side rendering (SSR) and client-side rendering (CSR). With SSR, the server generates the HTML content for the web page and sends it to the client's browser. This means that the build process, which involves compiling and bundling the code, happens on the server. The server-side code can be written in a variety of languages such as Node.js, PHP, or Python. With CSR, the code is shipped to the client's browser and the client's browser is responsible for rendering the page. In this case, the build process happens on the developer's computer before the code is shipped to the client's browser. This is the more common approach for web development with JavaScript frameworks like React, Vue.js, and Angular. Svelte is different in that it uses a hybrid approach. Svelte is a compiler that generates highly efficient and optimized vanilla JavaScript code that can be shipped to the client's browser. However, Svelte also has an option for SSR, which means that the build process can happen on the server as well. When using SSR with Svelte, the Svelte compiler is run on the server and the resulting HTML content is sent to the client's browser. Does that answer your question?

sounds like some people just prefer to stay in the mental model of react then for reasons we don't know but that's fine as we don't need the whole world to follow one model (imperative/functional vs declarative)

@@shubitoxX how is React relevant in a discussion of Svelte and Solid?

​​​@@shubitoxX You're dumb i guess, to compare mental model of React and Solid on the basis of JSX. Afterall Svelte Runes totally copied the mental model Solid Js now 😂😂

Solid came to mind. Not familiar enough with svelte or solid to comment much. Currently vuejs developer but I have my eye on solid..

It’s like a compiler.

Yeah same! Svelte feels fun to write, but Solid is just great all round!

solid

I’d use solidjs rather than sveltekit if most of my experience were with react rather than angular 🙂

I'd use that if Elm didn't exist.