Nominal Types in WebAssembly

Three prevailing themes in the discussion

Theme	Key points	Representative quotes
1. Adding nominal types & GC support to WebAssembly	The community is debating whether WebAssembly should expose a richer type system (nominal types, structs, rec groups) to enable garbage‑collection and type safety. Some see it as a natural evolution, others view it as unnecessary complexity.	• “Andy jests, but I would actually like to add nominal types to Wasm (along with type imports to make them usable). No proposal yet, but maybe later this year.” – tlively • “WebAssembly needs to know the structures of heap objects so that a GC can trace them and also to preserve type safety when accessing them.” – tlively • “webassembly adding nominal types is like watching a toddler slowly reinvent java.” – elophanto_agent
2. Performance & portability skepticism	Many participants question whether WebAssembly truly delivers on its promise of “portable assembly.” Concerns include lack of native speed, the overhead of complex types, and the comparison to existing binary translation layers. Others counter with evidence of near‑native performance and real‑world benefits (e.g., cold‑start reduction).	• “WebAssembly is becoming another JVM. It's not simple. It's not fast. It's not easy to use.” – kjksf • “My emulators here have roughly the same performance as the same code compiled as native executable (e.g. within around 5%).” – flohofwoe • “Using WASM can minimize cold startup time for serverless functions.” – zffr
3. Syntax & readability of the WebAssembly text format	The discussion touches on how WAT (the text format) is written—whether it should be S‑expressions, structured assembly, or a hybrid. Some users find the current format confusing, while others explain its historical roots and practical usage.	• “Real‑world WAT looks more like this (it looks like a ‘structured assembly’ type of thing).” – flohofwoe • “The standard text format also allows the instructions to be nested as S‑expressions.” – tlively • “S‑expressions are only used outside such instruction blocks for the ‘program‑structure’.” – flohofwoe

These three themes capture the core of the conversation: the push for richer types and GC, the debate over performance and portability, and the ongoing discussion about how WebAssembly’s text syntax should be written and understood.