A NES emulator written in Odin

(lucypero.com)

114 points | by frostbyte7 18 hours ago

7 comments

  • boltzmann64 16 hours ago
    i love odin.

    - manual memory management

    - arena and pool allocators

    - go style err!=nill style exception handling

    - first class support for soa and vectorized simd, linear algebra and swizzling

    - sanely typed and namespaces

    - explicit unambigious overloading, subroutine context

    - first class support for defer statements

    - zero friction C ffi

    if you haven't heard of odin, you should definitely consider it.

    • jazzypants 14 hours ago
      > - go style err!=nill style exception handling

      Is this not widely considered to be the ugliest part of the language? Why do you prefer having to do this manually?

      • iaaan 13 hours ago
        As someone who is primarily a Go dev, I never understood this criticism and have never seen a language do it any better (but I'm open to suggestions). I think try/catch is worse. I kinda like JS's promise syntax with the `.then()` and `.catch()`, but it doesn't appear that different to Go's approach.
        • sn9 11 hours ago
          Returning Result/Options that the compiler forces you to check so you can't forget.

          Common in ML-family languages and Rust. They've been brought into most mainstream languages like Java by now because of how useful they are.

          • wahern 6 hours ago
            You don't necessarily need a result/option type. Go could add a dependent typing facility that let you express a relationship between the first and subsequent return values.

            Very few languages do that; an option type is simpler to implement in many respects. But in the case of Go, especially at this juncture, it's possible the simplest route is a dependent type, at least a specialized one. You don't need to introduce a fully generic dependent typing facilty.

            Even simpler would just be type qualifers, e.g. optional or nilable, on the first return value, though that doesn't help with multivalue returns, where a simple dependent typing facility could fully express success vs error return semantics.

            You could also do it with contracts, though more obliquely. One of the criticisms with C++ contracts was that a contract made it easier to optimize a routine for the declared relationships, but without absolutely mandating enforcement that the callee or caller also obeyed the contracts, which is more difficult to do. That meant there was the potential for contracts to result in more bugs caused by interactions between undefined behavior and the optimizer.

          • HeavyRain266 10 hours ago
            Odin has @(require_results) that forces you to do something with returned values (e.g. T, Maybe(T), (T, bool))

            Where Maybe is a polymorphic union of T and nil but the core library returns either (T, bool) or (T, E) where E is an error enum.

          • iaaan 9 hours ago
            Ahhhh, got it: enforced correctness. Fair enough, I can definitely see the benefit of that. I do wish Go had more ways to do that, like first-class enum support, exhaustive switch cases, and, yeah, forced error handling. golangci-lint does a lot of this heavy lifting on behalf of the Go compiler, but it would be nice to have the compiler enforce it.
            • slifin 8 hours ago
              I hope that doesn't mean the compiler inherits the extra work

              I'm considering glojure as an interesting new hobby language to try because it's benchmarks are impressive

              If the go compiler ends up bloating itself with checks its static analyser could/should have done it would be a shame

              • iaaan 1 hour ago
                I mean that I run an external CLI tool called golangci-lint (a linter), and it does some things that the compiler arguably should do instead.
        • vips7L 12 hours ago
          Personally I think Go style is worse, because the runtime and compiler don't force you to handle the error. I just had to fix a critical issue because a dev forgot to check the result coming from a function, exceptions would have forced it to happen.
        • Tadpole9181 10 hours ago
          > I kinda like JS's promise syntax with the `.then()` and `.catch()`, but it doesn't appear that different to Go's approach.

          These days async/await is first-class and the function-based callback form of promises is largely discouraged. And for, at least in part, the same reason: it's harder to enforce correctness.

      • ixwt 14 hours ago
        It is, which is why the or_return[1] keyword was created.

        [1]: https://odin-lang.org/docs/overview/#or_return-operator

      • wolttam 12 hours ago
        Errors as values instead of some special language construct is generally a nice thing (IMO)
        • vips7L 12 hours ago
          Exceptions are values. There's nothing different between:

              T someFn() throws E;
              fn someFn() -> Result<T, E>;
              func someFn() (T, E)
          • Dr_Emann 12 hours ago
            In only one of those examples do you get a T that's invalid.
            • segfaltnh 11 hours ago
              True, Go does require you to follow a convention here (dont use T if err is not nil). In practice it works pretty well, though obviously not bullet proof.

              I believe some exceptional languages are similar, like Ruby. If you rescue but dont abort, the variable on the left hand side gets a nil when that may otherwise not be possible. Of course, that is handled cleanly as its own error.

            • vips7L 11 hours ago
              I don't see how. Unless it's the Go example where you get (nil, err)?
      • 12345hn6789 7 hours ago
        Yes it is and it's frankly odd we are still designing languages this way. It's a mess and a Result with typed errors is much more ergonomic and should be the standard. See either in scala for more.
    • christophilus 15 hours ago
      LLMs are pretty good at it, too. I recently had Haiku rewrite all of my Quickshell Linux UIs (dux) to Odin + an immediate mode GUI library: launcher, Niri bar, WiFi manager, process manager, lock screen, HUD audio/brightness, etc. Did all but the process manager in a day, while I was spending 99% of my time paying attention to my day job.

      Anyway, Odin is my favorite of the new systems languages. Lightweight, ergonomic, decent stdlib. It’s quite good.

      • christophilus 12 hours ago
        For the record, the library I used was Skald[0]. It's decent. Not 100% fully featured yet, but performant and fairly low resource, especially compared to Quickshell.

        [0] https://github.com/BuLEEto/Skald

    • DASD 15 hours ago
      What's the decision-making in choosing Odin over something similar like C3 or Zig?
      • Verdex 14 hours ago
        I can't speak for the implementor. And for that matter I also don't know what facilities c3 and zig provide.

        However Odin comes prepackaged with a lot of bindings for helpful 3rd party libraries. Likely makes this sort of work a lot less tedious.

      • vconnor 14 hours ago
        I have tried all three, and I chose Odin because I prefer the syntax (especially over Zig) and the vendored libraries are a killer feature for me. You get a lot of graphics, maths and gamedev-adjacent packages with the language, that can take you very far without having to shop for third-party packages.

        Odin for me is the (low level) systems language nirvana, along with Elixir which is my distributed system nirvana. They spark so much joy.

      • fuzztester 8 hours ago
        maybe stability or completeness?

        C3 and Zig are still evolving. Not sure about Odin. Check it.

    • varispeed 9 hours ago
      Why not just use C?
      • sitzkrieg 6 hours ago
        odin is way more ergonomic than any c standard
    • Panzerschrek 2 hours ago
      > manual memory management

      Ergo memory leaks.

      > arena and pool allocators

      A poor's man replacement for RAII.

      > go style err!=nill style exception handling

      Literally the most criticized part of Go.

      > first class support for defer statements

      Again, defer is used, because there is no RAII.

      > consider it

      No, thanks. I will continue using Rust or even C++. I don't want wasting time debugging memory leaks and corruptions.

      • boltzmann64 40 minutes ago
        there is definitely a tradeoff here: would you rather hunt for memory leaks or hunt for references (to satisfy the borrow checker).

        some of really want to do it the old way with arena/pool allocators than guarantees at the compile time. odin's target audience is not rust programmers, it's C programmers who want modern conveniences.

    • phplovesong 13 hours ago
      Did not C3 basically render Odin useless? Its basically C that did not stagnate in the mid 90s.
      • ternaryoperator 38 minutes ago
        C3, Odin, Zig, and many other languages are all competing to be the ergonomic replacement for C. None of them has crossed the chasm to wide industry adoption, so there is not one of these that, to use your words, renders the others useless...yet.
  • AdmiralAsshat 15 hours ago
    It's always interesting when the article title betrays the author's origins. I assume the author speaks British English rather than American English, because they tended to pronounce "NES" and "SNES" as acronyms ("Ness" and "Sness"), while we Americans tended to treat them as initialisms ("En-ee-ess"). So to my American eyes, I would have expected "An NES emulator" instead of "A NES emulator."
    • forgotpwd16 14 hours ago
      Could also be native vs non-native English speaker. Especially in computing world, it's common for non-native English speakers to utilize American spelling/punctuation while grammar/pronunciation is influenced by their native language. This appears in this post, and, arguably, even the title. In many languages (incl. Spanish, probably author's native language) acronyms are read phonetically.
    • dwb 13 hours ago
      I always heard it “nez” and “snez” actually (south western England)
      • masfuerte 11 hours ago
        And in the Midlands. Ness is Nessie's home.
    • hobo123 11 hours ago
      I've also read people refer to the "Super Nintendo".

      My friends and I in Germany always called them Nes and Super Nes.

    • HeavyRain266 13 hours ago
      Author is Argentinian, I guess they teach British English in schools out there.
      • cubefox 13 hours ago
        Yeah in Argentina they probably teach the kids that NES is pronounced "ness" during English lessons.
  • typicode 10 hours ago
    The hardware from this era is always super interesting. Having circuitry in cartridges + in the console is wild when you think about it.

    Nice to see other languages being used :)

  • Dwedit 7 hours ago
    How does Odin compare with C++, Zig, or Beef?
    • andyfilms1 7 hours ago
      C-like performance with a lot of modern conveniences and fairly straightfoward syntax. Lots of vendored libraries included. Makes worse burgers than beef.
  • anthk 16 hours ago
    Odin needs too recent LLVM versions to work. A pity this Reticulum client it's written on that, because if it were written in Go it would be instantly portable to legacy machines:

    https://github.com/Quad4-Software/Ren-TUI

    Reticulum in Go:

    https://github.com/Quad4-Software/Reticulum-Go

    On Odin itself, it looks really simple, and I'd love it if it were self-bootstrapable or compilable with just a C99 compiler like cparser, cproc or TCC.

  • fuzztester 8 hours ago
    Related: What are other C-like or systems programming languages other than Odin, Zig, C3 and Hare?

    I have checked out all 4 some, only by reading the docs and examples so far.

    Uneasy about Zig because of docs lagging code, and syntax.

    Hare is Linux only. Doable, but prefer Windows too.

    Need to try Odin.

    Other interesting langs in this space whih are at a somewhat usable state, including docs and libs? I don't need a package manager or an LSP or much other tooling.

    For now this is just for developing small apps of my own.

  • reilly3000 12 hours ago
    Among all of those interesting learnings, I suspect they will soon be learning the legal code too. Nintendo of America defends its IP ferociously and too excess.
    • luxurytent 12 hours ago
      What can Nintendo do if someone builds an emulator?
    • segfaltnh 11 hours ago
      Yeah this is true all the other emulator authors are in jail.

      Source: onion article

    • debo_ 12 hours ago
      Yes, Nintendo famous for hunting down hobbyist NES emulators. Give me a break.