5 comments

  • the__alchemist 6 minutes ago
    In 2026: Please don't learn this; it's obsolete. Learn Vulkan (Or another modern API; or how to build engines on top of them; or how to write shaders; or how to do GPU compute using CUDA etc)
    • criddell 3 minutes ago
      It's so much easier than Vulkan or writing shaders and the performance is more than good enough for a lot of applications.

      I wonder if somebody has written a adapter layer to write old OpenGL and translate it on the fly to Vulkan?

    • samiv 5 minutes ago
      OpenGL is not obsolete and is totally fine for many use cases. Vulkan is way too complicated and cumbersome for many.

      Even if OpenGL doesn't get new features what exists now will continue to work for decades.

      • flohofwoe 0 minutes ago
        The problem with OpenGL isn't so much that its programming model is outdated, but that it is an incrdibly confusing and just plain badly designed API, mainly because the various sediment layers that have accumulated over 30 decades are not clearly separated (Vulkan is starting to suffer from the problem btw, it's apparently some sort of Khronos curse).

        On Windows, starting with D3D11 makes a lot more sense, or on macOS with Metal v1. Both APIs are 'close enough' to modern 3D APIs to transfer a lot of the knowledge over, but without being too low-level like Vulkan or D3D12.

      • reactordev 3 minutes ago
        [delayed]
  • MoltenMan 30 minutes ago
    Man, this takes me back! I made a Minecraft clone called Mindacraft in Java using LWJGL (the same framework Minecraft uses) about 6 or 7 years ago using this tutorial. I vividly remember this tutorial being the most useful resource for OpenGL by an order of magnitude, and that was with it being written in a language that actually had pointers and buffers! (Using OpenGL in Java is very weird because you have to use pointers and buffers through a bunch of wrapper classes, and it makes things a lot weirder. It's like using unsafe in Rust if unsafe wasn't even in Rust).
  • AyanamiKaine 29 minutes ago
    If you want to use the learned knowledge I would recommend to use something like Sokol [0] or use the SDL-GPU API [1]. While Sokol is more higher level both can be used. Otherwise learn opengl is a really good introduction.

    [0] https://github.com/floooh/sokol [1] https://wiki.libsdl.org/SDL3/CategoryGPU

  • AspisAiantos 31 minutes ago
    I've gotten through the Getting Started section and found it to be quite good overall. A few times it seems to make some jumps back and forth between slightly different setups, which might lead to some problems debugging.

    I definitely recommend it to anyone interested! Honestly one of the biggest things it helps with is explaining the setup boilerplate for OpenGL.

  • SomeHacker44 29 minutes ago
    Any recommendations on how to use OpenGL from the CLR (.Net/C#) please?
    • Sleaker 17 minutes ago
      Typically just find bindings for your language and adapt the startup/bootstrap to match your language syntax. Opengl calls are fairly agnostic especially when you move to the shader logic.

      The biggest issue with c# dev is OS specific window management. CLR doesn't have good wayland support yet if you're trying to do this from a modern Linux distro.