Raylib 6.0 ships a CPU-only software renderer (rlsw), four new platform backends, redesigned animation/fullscreen systems, and 600 total API functions.
Key Takeaways
rlsw software renderer implements OpenGL 1.1+ in a single-file header by @Bigfoot71, runs 30-60 fps on basic scenes with no GPU or external dependencies.
Enables raylib on ESP32 microcontrollers (Espressif port already live) and upcoming RISC-V devices with no discrete GPU.
New platform backends: rcore_memory (headless framebuffer rendering, useful for server-side graphics), rcore_desktop_win32 (direct Win32 API, no GLFW/SDL), and a new Emscripten backend dropping libglfw.js.
Skeletal animation redesigned to support blending between frames and animations, with GPU-skinning optimizations and updated Model/ModelSkeleton/ModelAnimation structs.
File system and text management APIs consolidated into rcore (40+ fs functions, 30+ text functions); utils module removed, library now compiles from 6-7 .c files.
Hacker News Comment Review
Community sentiment is strongly positive and personal: commenters describe raylib as the library that made programming feel fun again and enabled them to actually finish projects.
Practical cross-language use is confirmed: at least one commenter is shipping a Swift roguelike via C-interop, suggesting the C ABI compatibility is a real production path, not just a curiosity.
The ESP32S3 software renderer angle drew immediate interest from embedded/hardware builders, consistent with the release notes’ framing of RISC-V and no-GPU industrial targets.
Notable Comments
@forsalebypwner: plans to test the software renderer on ESP32S3 specifically, validating the embedded use-case as a real near-term target.
@alex_x: shipping a roguelike in Swift via C-interop with raylib, confirming non-C language bindings are production-viable.