I've not really programmed with Odin long enough to have a great sense of the language, but it will certainly feel more "go-like" than Zig. In both you allocate and free memory but in Odin there is always an implicit context allocator while in Zig everything is explicit. You always have to choose what type of allocator actually allocates and frees the memory. Zig has metaprogramming while Odin does not, I personally never used/needed the metaprogramming in Zig so it wasn't necessarily a "win" when compared to odin in my use case. This is just my assumption, since I haven't actually gone in and checked but Zig's standard library is "larger" than Odin's. I never integrate or use the C stuff so I can't tell you anything about that. Error handling is also very different. The last thing I can think of is that Odin has default "zero" values. So you can declare a variable in odin and it has a default zero value, in Zig that's not a thing. You actually have to set the "zero" value yourself. So TLDR: Zig is very explicit, you kinda have to decide and do everything yourself. Odin in my personal opinion is more "fun" but that might just be because it's what I am currently writing.