Видео

For someone new to Odin, the use of ^ instead of * looks odd.

I'm going through core:io but I'm pretty lost with getting user input from stdin. Maybe you could please consider putting a section in your book.

Awesome channel! Can't wait for the book!

I loved smash it. So this is the artist huh? Wow. I just discovered tear down on RUclips and was intrigued by the physics which adds to an important realism which is fun and familiar. Just like the real world.

Thanks

Great explanations about memory leaks and a very clever solution to this problem proposed by the Odin language! Very interesting. Thanks Karl

Thanks Karl for the excellent video series. However I have to offer some alternative advice. There are many languages that disallow cyclic dependencies between packages (or modules, or namespaces depending on what the languages call their organizing concepts). Go, Rust, and Haskell, for example strictly disallow cycles, Java and Scala I believe may allow them but it's problematic. Same with the .NET family of languages. The problem of code organization and dependency management is mostly independent of language. What it takes is planning, forethought, and conscious, intentional design. If you're learning a language, working in a new / unfamiliar domain, or are simply not very experienced, you are probably not in a position to plan a large complex project very well, so you will have problems organizing (via packages) your code correctly right out of the gate. This is one of the most obvious advantages highly experienced engineers bring to a project - experience around large project code organization. Dropping everything in a single package/namespace is an easy "solution" because it effectively ignores the primary mechanism for code organization and relies on globally unique naming instead. This non-organization method of organizing code is useful for everything from toy projects, demos, and learning examples to smaller production projects run primarily by one person or a small team. Small games, command line utilities, wrapping existing libs from other languages, things like this are small enough that you may not really need to organize (via package/namespace) the code. Once you get into larger projects involving large / multiple teams and hundreds of thousands or millions of lines of code, you better have a well developed philosophy about code organization, and it will involve multiple packages with carefully considered interdependencies, which allows for sub-teams to work more independently (which means quickly), work to a "contract" (or interface, or API), isolate the impact of code changes, make it easier to build discreet and focused tests, and many other benefits. It's good do introduce these concepts early in a software engineer's growth, so that these concepts and practices become engrained early. Because you're right that code organization done wrong is worse that no code organization. But no organization (or minimal, ad-hoc, unplanned organization) is limiting in proportion to the size of the project and team.

Starting a C++ project is pain 😢.

Your contents makes Odin and low level programming in general less scary. Thanks a lot Karl ! Ill buy your book once it comes out for sure !

👍 great. But how do I run it in vs code?

One thing I recently learned the hard way while using pointers for the first time: if you accidentally let the memory that your pointer refers to get freed, then your pointer becomes bad (a dangling pointer), and now points to some random memory. The code might crash, or it might do something weird that drives you crazy. This confused me because I didn't understand the difference between a nil pointer and a bad pointer. At least Odin initializes the pointer as nil so it isn't bad to begin with (a wild pointer), unlike C/C++.

Thanks Karl. These short single subject videos are great. They are easily digestible which is especially important for subjects like pointers that are notorious for tripping up people new to programming. Keep up the good work.

Looking forward to your book!

Thanks for the video! :) Looking forward to your book. Quick question. With my understanding, if you pass a struct to a function (not as a pointer) it will make a copy of that struct, like a value type, yes? So should we always be aware to pass it as a reference, even though we might not want modify the struct inside the function itself? Or is it fine to pass copies around, if we're not modifying it. Hope it makes sense.

I just want to say a big thank you to you! You've really helped with me getting into and understanding Odin. I'm a go dev by default but have been having a blast with Odin, especially with raylib. Looking forward to reading your web book. 😁

what would be nice is a stack trace too. Knowing where the alloc is 50% but the other half is HOW it got there.

Something so satisfying about low tech game dev. Really enjoyed it, thanks for sharing.

i love it!

C# is getting the discriminated unions in the next release, most likely.

Heavily dependent on odin vendor libs. Anything that is pulled from third-party will still need to have some sort of build system.

how did you fixed your problem on your video called Getting Odin Language Server + Sublime to work at around 39:06? Thank you!

Thanks! Everything worked like a charm!

Great video! Thanks for the tutorial!

1:17 this is one of the weirder language decisions. to me it makes little sense why iterating the string uses a different data type than slicing it or reading its length. most of the standard library provides functions with a _byte suffix for when you do actually want to operate on a string in bytes instead of runes (which is probably a rare event). maybe string should be an alias for []rune (and cstring for []u8) so other functions behave consistently?

Nice video and interesting view on this. I don't know your background but I think that is needed to give little more time to adjust to this way of organization. My background is from go and when I was starting I had the same opinion, but with more experience and revision of seniors codes it just make sence and now I maybe using it too much. There is also difference in go if you want to make something private you need to hide it in directory, there isn't option to make it provate for file.

I was torn between Ada and Odin, and I eventually started playing more with Odin because even though it doesn't have headers, its gets very, very close with specification files (which are header-like, basically. it is basically module and package sugar). If it wasn't that, I would say tagged unions. They are just the best model for anything stateful/finite but easy to pass/manipulate by value.

Folks who are on Windows, you can use scoop to install and keep odin updated.

who thought graphemes were a good idea? i doubt they were a programmer. you can never get away from dumb decisions someone made in the past.

Very concise and insightful explanation, helped me a lot visualizing the level editor for my 2D top down game. Thank you very much!

I like how you explained fixed timestep physics, but in a game like this, I think it's better to just clamp "dt" to some reasonable maximum. Like slowing down time when the game can't keep up.

Do you know how to get the odinfmt formatter to work as well?

The way I treat any string of bytes is to check is it a valid markup for what am I reading? and stick to the simplest format that can fit its markup into 1 byte, or just ascii. Anything else is either user's data and should be passed-through as is.

thanks.

Hmm JavaScript shows "小猫咪" as 3 length so it has no problem with processing it normally. Emojis though it struggles with. Like 👵 is actually two emoji/characters (old person + female), but (and despite showing the `.length` as 2) it can't split them. Though having worked with a project that dealt with splitting and recombining emojis I definitely felt there to be a need for better handling of such "multi-cellular" characters in the language. "Runes" sounds like a great concept to deal with these things.

Nice and concise! Love how these videos feel super chill while covering interesting language features the sublime presentation just adds to it, clear examples without needing to parse huge walls of text :)

> rune_count > chinese characters missed opportunity to call them moonrunes

Thanks for yet another focused and informative video 👍