Not all. One mentioned in the article, Qwik, uses a different technique the authors call resumability. It’s similar in that it applies JS to components client side which were rendered with the same code server side. The subtle differences:

- it derives its initial client state from the HTML, rather than re-running the initialization which already ran on the server

- it doesn’t render top down, it resumes interactive components on demand (on first user interaction by default)

- it doesn’t load any of that code at all by default; if your page is fully static, none of the code ever gets loaded

This is similar to frameworks like Astro which use a technique called “partial hydration”, but with Qwik it’s handled by the compiler. Another which is somewhere in between (and has been doing all this for years; I’m not sure exactly where its most recent release sits on the spectrum) is Marko.