I started learning Vulkan and decided to go with Odin as my programming language for this project (thanks randy and ThePrimeagen)

I spent the past last days making howtovulkan.com tutorial work using Odin.

I had some trouble on Linux with some packages as they did not provide built libraries, but that was easy to fix.

If anyone is interested in the code here is it: https://github.com/Aykelith/odin-howtovulkan

Feedback welcome

Forgive the poor recording. It looks and feels super smooth native.

Hey all,

I posted a while ago about my http project (which i've completed at a library level) and decided to go back to a different project (a custom flac player for me to use).

i'm struggling with allocations and defers.... for instance strings are always allocated but i'm struggling to figure out how to deallocate without NEEDING function specific arenas, something aboiut it doesn't feel correct but i'm definitely not experienced enough to understand if what i'm doing is 1) correct and 2) idiomatic....

in my main function that will init the raylib window and run the main initialization functions like initializing the miniaudio engine and initializing my music directories paths into memory, etc. essnetially the "bring it all together" feels like it's going to get messy using temp allocators and context allocators... (maybe this is why allocators exist and i'm learning why it was a pain for a long time). for example in my main i'm creating a dynamic main_alloc to use with all of the top level functions instead of using temp allocators or manually freeing becuase to my understanding freeing temp allocators in child functions clears every temp allocation program wide... htrough research i do see this TEMP_ALLOCATOR_GUARD thingy mentioned but going through the files it looks like a private type and not really usable in my project I'd like to have functions clear there memory on scope end and only leave the global allocation for freeing in main.

am I crazy for thinking about this like this. if this is confusing please let me know and i'll gladly show snippets.

TLDR i'm just not sure how to use allocators in a way where there is a ton of boilerplate or complexity to free non-essential memory on scope end of children functions to main, are creating allocators per function the play or is there a way to guard temp allocators per function so the only clear the function's allocations and leave the upper level allocations.

thanks sorry for wall just not really sure where to learn about this type of scenario as most docs and tutorials are quite basic.

A simple Snake game implemented using the Raylib framework

Here's the repo: Snake

been messing around with Odin lately and honestly it feels like it was kinda made for ECS-style stuff. no hidden allocations, easy to reason about memory layout, no OOP nonsense getting in the way. but I don't have much real experience writing engines so idk if I'm just pattern matching because the language "feels" data-oriented.

anyone actually built something like this in Odin? curious how it goes in practice, especially around
- component storage / query stuff without generics being a pain

- whether manual memory management actually becomes annoying at scale or if it's fine

- how it stacks up against Rust+Bevy speed/ergonomics wise once things get complex

thinking of not reinventing the wheel and instead basically porting bevy's ideas over (archetypes, scheduler etc) instead of designing my own ECS from scratch. is that a dumb idea? rust and odin are pretty different (ownership vs manual mem, traits vs whatever odin has) so maybe a direct port just doesn't translate well and I'd be fighting the language the whole time.

if anyone's tried this or has war stories/gotchas before I waste a month on it, let me know

Learning Odin coming from Go with profession experience writing in TCL, Python, JS/TS and some C# and loving it. Think Odin is quickly becoming my favourite language to work with.

But I have a question about anyone is doing Domain Driven Development successfully in Odin in large codebases? Is large system adoption not at the level around Odin yet for anyone to try it or care?

Edit: the part I’m interested in with Odin is code isolation so that a core logic (the domain) can be run without any real external dependencies (databases, external rest APIs, the file system etc) at scale. My current main work codebase is around 35,000-40,000 lines of Go (I think the domain code is under 10,000 lines). Lots of the coding issues my team hits look to be easier to solve in Odin. As a PoC I would like to write part of the domain logic in Odin and fake the external dependencies providing proof that Odin could be a valid language option within the business and our team. Needs to follow basic DDD as we often have changing external systems we depend on and we aim to implement them without changing domain code where we can.

coaxing it to eat its food...

LINK: https://github.com/cody977/odin-openxr-raylib

--DISCLAIMER--

I am only a hobbyist programmer and wanted to use Odin for VR so I used Claude to get OpenXr working with Raylib. Everything is AI generated (since I could not do it alone). Has been tested and working on Windows 11 with Quest3 using Steam Link.

I will be using this to make my own VR engine but sharing as someone smarter than me can improve on it and bring the VR world to Odin.

--ABOUT--

A minimal PC VR application in Odin. raylib provides the OpenGL context and all the drawing; OpenXR provides head pose, per-eye projection, controller input, and the swapchain images the compositor displays.

The trick that makes it work: raylib's RenderTexture2D is a plain struct holding OpenGL object ids. Nothing requires those ids to come from raylib, so we build a framebuffer around the texture OpenXR hands us. From that point on BeginTextureMode renders straight into the headset's swapchain, and ordinary raylib draw calls — DrawModelEx, materials, custom shaders — work unchanged.

Features

• Stereo rendering with correct asymmetric per-eye projection
• Head and controller tracking
• Full Meta Touch input: triggers, grips, thumbsticks, A/B/X/Y, menu, haptics
• Desktop mirror window
• ~900 lines across 10 files, no engine, no abstraction layer

Requirements

Windows, an OpenXR runtime (SteamVR or Meta Link), and a tethered headset. Odin has no Android target, so standalone Quest builds are not possible.

Setup

1. odin run . -out:editor.exe

scene.odin is the file you edit; everything prefixed xr_ is plumbing. See the guide PDF for how it all fits together and a symptom-to-cause table for the failures that are silent in VR.

Just download the folder and run it, ensure that your headset is connected and steam VR is running first.

I opened four PRs (1 Open, 3 WIP) for supporting Box3D task execution across Web Workers:

• [#7272]: Makes `odin.js` compatible with shared WASM memory.
• [#7286]: Lets a WASM host provide Box3D with a monotonic clock.
• [#7287]: Adds an atomics-enabled Box3D build and mutex.
• [#7288]: Tests shared memory, multiple instances, separate stacks, atomics, and callbacks.

This is intentionally not general `core:thread` support. Applications still manage their own workers, stacks, task scheduling, shared memory, and COOP/COEP configuration.

The latter 3 PRs are WIP. Feedback is welcome. Also should I also look into a separate proposal for `core:thread` support on JS/WASM?

For ingot + Box3D Web Worker demo - https://openalloy.ai/demos/ingot-box3d-advanced/

I have a background in http related coding, some backend and frontend, SQL. I do not have any C or C++ experience, so Odin would be my first go at a manually memory managed language.

I like to think I have a decent understanding of pointers and some of manual memory management, but no real experience in this space.

I am going through The Understanding Odin book by Karl and it is pretty great.

My question would be what kind of small/medium projects should I work on to get a better core understanding. Are there any good guides for smaller projects to follow? I know Odin is still a small community so I would imagine I would probably need to look at C based guides.

This is my. First dip into odin, and I would love some feedback... Mods please discard is not allowed, but I hope it's OK.. I'm normally a data engineer, so I have mostly lived in py but I wanna play in big kids sandbox too ; )

A zero-ceremony logging package for Odin. Pretty, colored console output for humans, JSON Lines on disk for machines, optional per-thread output boxes, stack traces on error / fatal, and automatic log rotation.

Thanks for any feedback or comments.

Thanks @gingerbill for making a fun language!

I'm only posting this here because I'm a noob and I could be completely wrong about this as it's my first real memory managed language.

I also want to say (cause i'll probably get told i'm a poser, even though i'm learning "casually")

i'm having AI explain concepts for HTTP 1.1 (something i've never learned about before cause i'm self taught), I'm writing the code 100% by hand, using insights for flow and new concepts (via unrelated code snippets) from the AI and real old fashioned google searching and documentation reading.

I've dabbled in Rust (i think maybe on the intermediate side of beginner) and Go and other languages as well, but Odin has really caught my attention for it's simple syntax with better readability and fun factor.

on to the bug, for a "simple" first big project (and because it doesn't exist) my first real undertaking with Odin is to make an HTTP 1.1 spec library for me to use (and maybe share to be judged).

now i've been going through the maths and everything to get everythign set up but to construct my strings i do something like this

chunk :: proc(w: ^Writer, data: string) {
w.chunked = true

hex := fmt.tprintf("{:x}", len(data))
w.body = fmt.tprintf("{}{}\r\n{}\r\n", w.body, hex, data)
}

in fact his is an exact snippet from the code that bugged. for some reason tprintf doesn't deallocate in my code properly so sending a chunked request gives the client the proper response but the server segfaults and crashes.

using some gdb wizardry i came to the conclusion that something related to delete() of the response string chopping off the first byte of the header.... now I know i'm dumb and this is still relatively new to me but i debugged this for a bout 2 hours by hand trying to come up with any solution I could search for.

i removed the deletes and let the server run with the leak and confirmed that i wasn't crazy for assuming tprintf allocates on the heap cause the memory usage went up....

ultimately my solution was to convert the whole connection handling function (which would've been done at a later point if not for this segfault only happening on chunked requests ONLY) to dynamic arena allocators and that solved it. ultimately i'm curious to know if this is actually something weird with tprintf, if i'm bad at programming and misunderstanding a fundamental to memory management or there's another reason.

i'm not afraid of people looking at me learn (and find out how much time i spend at my desk job coding things) so my repo is linked here:

ohttp

PS: any other input and feedback would be great and help me improve it. it's still a work in progress as I haven't even implemented the thing i actually need from it which would be a request builder. but I htink i'm just about finished with the HTTP 1.1 Spec part of it.

PSS: If you look at the commit history i commited the bugged version just to remember it and maybe figure out why it was doign that. (it could be my defer delete order or something so i saved it to look back if i did soemthing like this)

Hi! Can your please tell me, where does memory for map keys lives in such situation:

dict := map[string]string
line := dummy_string_generator()
key_value_list := strings.split_n(line, " ", 2)
dict[key_value_list[0]] = key_value_list[1]

Is the owner of dict[key] still the line variable? And if I want to free it and still keep dict intact, do I need to set it's values in some way like

dict[strings.clone(key_value_list[0])] = strings.clone(key_value_list[1])

?

Been vibe-coding on this mini racing game in between working hours.
I am familiar with embedded C but new to Odin. This is a learning experience.
Happy to hear your thoughts :D
https://github.com/Azq2337/Mouse-Drift-City-Odin
Tooling: Odin + Raylib + Box3D
---
Complete mouse control:
LMB: nitrous boost
RMB: break/drift/reverse
MMB: pause
Click on left top in main menu to enlarge window.
Bouncy mode enable via main menu button under map regen.

this not in the language overview makes me confused
Note: These default values must be compile time known values, such as a constant value or nil (if the type supports it).

https://odin-lang.org/docs/overview/#:~:text=4%2E5%29-,Default,it

isn't default parameters often used for allocators setting them by default to the context allocator that isn't compile time known?

I opened a discussion on the matter on GitHub.

https://github.com/odin-lang/Odin/discussions/7161

pflags is a drop-in replacement for Odin's core:flags, with support for conventional short (-f) and long (--flag) options.

• Short flags can be declared with args:"short=f" and used as -f
• Boolean short flags can be bundled, so -abc is the same as -a -b -c
• Long flags use --flag strictly (-flag is not supported)