Raylib 6.0 ships a CPU-only software renderer (rlsw), new Win32 and Emscripten backends, redesigned skeletal animation with blending, and a consolidated filesystem/text API, now totaling 600 API functions.
Key Takeaways
Software renderer (rlsw): Single-file, header-only OpenGL 1.1+ implementation by Le Juez Victor runs purely on CPU, no GPU required; already ported to ESP32 and targets upcoming no-GPU RISC-V devices.
New platform backends: Win32 (direct Win32 API, replaces GLFW dependency path) and Emscripten (no libglfw.js dependency) added alongside a PLATFORM_MEMORY backend for headless server-side rendering to a memory framebuffer.
Skeletal animation redesign: Supports animation blending between frames and across different animations; GPU-skinning improved; Model, ModelSkeleton, ModelAnimation structs revised.
Filesystem and text APIs consolidated: All filesystem logic now lives in rcore; utils module removed; 40+ filesystem and 30+ text management functions exposed, enabling raylib as a build-system scripting foundation.
Build config overhaul (config.h): Features can now be disabled at compile time with simple -DSUPPORT_FILEFORMAT_OBJ=0 flags; useless flags removed, new ones exposed.
Hacker News Comment Review
Commenters are most excited about the software renderer’s embedded potential; ESP32S3 is the immediate target named, with RISC-V devices seen as the longer-term use case that motivated the feature.
Sentiment in comments skews toward hobbyist and indie builders who credit raylib with making game development feel completable rather than overwhelming, signaling strong retention in that segment.
A beginner question about raylib vs. Unreal/Unity surfaced but drew no technical response in this thread, leaving the capability gap undiscussed.
Notable Comments
@alex_x: Building a roguelike in Swift using C-interop with raylib, citing this release as a source of joy – concrete evidence of cross-language embedding in production hobby projects.
@forsalebypwner: Plans to test the new software renderer on an ESP32S3, directly validating the embedded use case the release notes highlight.