Overview

  • Open-source.

  • Created on (2016-07-07).

  • Overview .

  • Basic Examples .

  • FAQ .

  • Brief Explanation {10:02 -> end} .

  • Tips for searching information in the source code .

  • Features compared to other languages .

  • Philosophy :

    • Simplicity and readability

    • Programs are about transforming data into other forms of data.

      • Data structures are just data.

      • Odin is not OOP.

      • Odin doesn't have any methods.

    • The entire language specification should be possible to be memorized by a mere mortal.

    • Odin Market is Weird .

      • "The killer feature is that it has no features".

      • "bring them the 'joy of programming' back".

      • He ends the article by asking how to market the language, he doesn't know himself.

  • Paradigm :

    • Focus on the procedural paradigm.

    • GingerBill: "Odin is not a Functional Programming Language".

  • Roadmap :

    • FAQ:

      • There is no official roadmap. Public roadmaps are pretty much a form of marketing for the language rather than being anything useful for the development team. The development team does have internal goals, many of which are not viewable by the public, and problems are dealt with when and as necessary.

      • Odin as a language is pretty much done, but Odin the compiler, toolchain, and core library are still in development and always improved."

  • C Integration :

    • Odin was designed to facilitate integration with C code. It supports interfacing with C libraries directly and interoperability with other languages is facilitated.

  • Metaprogramming :

    • Odin offers some metaprogramming facilities, such as macros and templates, without becoming overly complex.

  • Compiler :

    • Written in C++.

  • Aimed systems :

    • Ginger Bill:

      • Odin has been designed specifically for modern systems: 32-bit and 64-bit platforms.

      • I highly recommend you don't use Odin, Zig or C for 8-bit chips; prefer a high-level assembly language instead.

  • Style :

    • We are not going to enforce any case style ever. You can do whatever you want.

Sources

  • Karl Zylinski .

    • Odin, RayLib.

    • Karl Zylinski .

    • Karl Zylinski on Odin and RayLib .

      • "Burnout with Unreal Engine".

        • No idea of what is happening in the engine.

        • Difficult and slow interaction.

        • C++.

        • etc.

      • "Odin fell into my lap and was perfect for what I wanted".

      • "Hot-reloading was the best thing I did; without it I would have gotten discouraged, because I am very impatient with iteration times".

        • Many things are in .dlls that are observed so if there are changes they reload, something like that.

        • "Don't necessarily create config files to tweak the game, but use code as data for tweaks".

          • Nah. Maybe if there is actual hot-reloading it can be okay, but a config file is very useful at times.

          • I think they are not mutually exclusive; config files are good for some things and hot-reloading for fast iterations.

      • "I made my own UIs, using Rectangles, with text inside, elegant borders, mouse hover system".

      • "I have fun and love the feeling of doing things from scratch".

      • "Why RayLib?"

        • "Reminder of how fun programming was in college when I was 22, now he's 36."

        • So, he didn't really answer the question.

      • Critiques of OOP, both from Karl and Wookash.

        • Nice.

        • Mentioned Mike Acton and DoD, etc.

      • Overall, the video is nice but doesn't talk about anything technical regarding Odin or RayLib.

  • Rickard Andersson .

  • Nadako .

    • Sokol, SDL, Vulkan, all in Odin.

  • Coding with Tom .

    • Odin, Zig.

Games and Apps made in Odin