The counter below was rendered on the server with a starting value of 3, and was then hydrated on the client to provide interactivity. Try out the buttons! Ooh

The counter below was rendered on the server with a starting value of 3, and was then hydrated on the client to provide interactivity. Try out the buttons! Ooh. We have supported this as a feature in the Qbix Platform since 2014: https://qbix.com/platform/guide/tools https://qbix.com/platform/guide/tools Back then, it was called “progressive enhancement” (anyone remember it?) before they moved to “graceful degradation” where JS was assumed always on (like broadband internet became assumed always on, instead of previous generation stuff like IRC that expected netsplits, now everyone just had SAAS on The Web with online/offline status). What we always advocated for is to build client-first software that works with JS, but then spend time to make versions that render on the server and work without it. In that order. Flips “progressive enhancement” on its head: https://qbix.com/blog/2020/01/02/the-case-for-building-client-first-web-apps/ https://qbix.com/blog/2020/01/02/the-case-for-building-clien... I gave a talk on this when I worked at Lab49, it might be more interesting in video form: https://youtube.com/watch?v=yKPKuH6YCTc https://youtube.com/watch?v=yKPKuH6YCTc