Very often these days I read about memory management as a differentiating factor. On one hand there's Rust with more "manual" memory management (I think) opposed to Go with its indeterministic GC pauses (see Discord blog posts about why they prefer Rust to Go because of that). On the other hand there's Go with its very simple automatic memory management. Where does Odin fit in?
I see that there are two paragraphs on memory management (https://odin-lang.org/docs/overview/#allocators) in the overview but they dive into the details very soon and don't really paint the big picture (I think the sentence "This means that Odin programmers must manage their own memory, allocations, and tracking" is not a great selling point, all other things being equal).
Comments
Very often these days I read about memory management as a differentiating factor. On one hand there's Rust with more "manual" memory management (I think) opposed to Go with its indeterministic GC pauses (see Discord blog posts about why they prefer Rust to Go because of that). On the other hand there's Go with its very simple automatic memory management. Where does Odin fit in?
I see that there are two paragraphs on memory management (https://odin-lang.org/docs/overview/#allocators) in the overview but they dive into the details very soon and don't really paint the big picture (I think the sentence "This means that Odin programmers must manage their own memory, allocations, and tracking" is not a great selling point, all other things being equal).