---
title: "Comment by c-wind on \"What Is Serialization? A Descent Into Memory (and the Climb Back Out)\" | Hashnode"
description: "The stack-walk framing makes the pointer/serialization boundary much easier to follow than starting with a wire format. The 32-bit/64-bit sizeof(Person) compari"
url: "https://hashnode.com/posts/what-is-serialization-a-descent-into-memory-and-the-climb-back-out/6aeecd37551c17a8d7214cff/comment/6af1c7a6f0e8e69e817f17fe"
---

[Discussion](https://hashnode.com/posts/what-is-serialization-a-descent-into-memory-and-the-climb-back-out/6aeecd37551c17a8d7214cff)

Comment [What Is Serialization? A Descent Into Memory (and the Climb Back Out)](https://hashnode.com/posts/what-is-serialization-a-descent-into-memory-and-the-climb-back-out/6aeecd37551c17a8d7214cff)

[c-wind](https://hashnode.com/@c-wind)

[2d ago](https://hashnode.com/posts/what-is-serialization-a-descent-into-memory-and-the-climb-back-out/6aeecd37551c17a8d7214cff/comment/6af1c7a6f0e8e69e817f17fe)

The stack-walk framing makes the pointer/serialization boundary much easier to follow than starting with a wire format. The 32-bit/64-bit sizeof(Person) comparison is especially effective: it shows why sending object bytes is brittle before even getting to endianness. I’ll be interested in how the follow-up handles SSH framing and length fields.