Proposal to Rename "Hydration" to "Functional Appending" in Next.js

[Dyonvangerwen]

Hello, Next.js Community!

As we continue to evolve and refine our understanding and use of web technologies, terminology plays a crucial role in shaping our thoughts and communications. The term "hydration," widely used across React and Next.js communities, describes the process by which static HTML generated by server-side rendering becomes interactive through client-side JavaScript.

Although "hydration" is well-understood within our community, I propose we consider renaming this process to provide a clearer and more intuitive understanding of what happens behind the scenes, especially for newcomers to the framework.

Proposed New Terms for "Hydration"

Functional Appending: This term clearly conveys that additional functionality is being appended to pre-existing HTML. It aligns directly with the process of adding interactive capabilities to static content.
Server-side DOM Mutations: This name emphasizes changes made to the DOM on the server-side before it becomes interactive on the client-side, highlighting the transformation aspect.
Active Appending: This alternative focuses on the activation of static content, suggesting a dynamic enhancement that brings the content to life.
Why Consider a Rename?

Clarity and Intuitiveness: Each proposed term aims to offer more direct insight into the actual mechanics of the process, making it more accessible, especially to those new to the field.
Educational Value: Simplifying terminology can demystify the process for new developers and those coming from different backgrounds, reducing the learning curve.
Technical Accuracy: These terms strive to more precisely describe the action of integrating JavaScript-driven interactions with statically rendered pages. They emphasize that the changes are both functional and incremental, affecting only necessary parts of the DOM.
Suggested Action
I believe adopting a new term in our documentation and community discussions could enhance our collective understanding and communication. I suggest we initiate a dialogue about this change and possibly consider a phased approach to renaming, beginning with educational materials for new users.

I invite all community members to share their thoughts, concerns, and support for this proposal. Let's collaboratively decide if a change in terminology could be a step forward for us all.

Thank you for considering this proposal. I look forward to our constructive discussion!