Best of C++March 2025

  1. 1
    Video
    Avatar of chernoThe Cherno·1y

    An 11-Year-Old Made a "Game Engine" // Code Review

    An 11-year-old named Anthony submitted his game engine project, 'Real Engine,' for a code review by Chenno. Despite being so young, Anthony managed to include a README, license, and instructions for his project. Chenno engages with the code, providing constructive feedback and corrections, particularly focusing on issues with precompiled headers and shader management. The post also highlights the importance of separating external dependencies into static libraries. Additionally, Chenno introduces the use of AI in code reviews through Code Rabbit, which can help in identifying potential bugs and improving code structure.

  2. 2
    Video
    Avatar of gamefromscratchGamefromscratch·1y

    Noesis Studio - The Ultimate Tool for Game UI Creation

    Noesis Studio has launched in free beta, offering comprehensive tools for game UI creation. It supports both Unity and Unreal Engine, has a lightweight C++ runtime, and uses XAML files for UI layering. Features include real-time updates, hot reload, data binding through view models, and extensive animation support. The studio allows seamless integration of vector and pixel art, and provides a modular, collaborative environment for developers and artists.

  3. 3
    Article
    Avatar of sandordargoSandor Dargo·1y

    C++26: Removing language features

    C++26 removes deprecated language features, specifically arithmetic conversions on enumerations and C-style array comparisons. These removals aim to simplify the language and make codebases cleaner.

  4. 4
    Article
    Avatar of lobstersLobsters·1y

    Why do I find Rust inadequate for codecs?

    The post discusses the author's preference for implementing codecs in C over Rust due to performance considerations. It outlines Rust's memory safety features and efficiency, but also highlights its limitations for low-level, performance-sensitive tasks such as codecs. Examples from existing codec implementations in PAQ8, bzip3, and LZ4 illustrate the performance-critical nature of these applications and how Rust's bounds checks and ownership model may introduce overheads. The author concludes that C remains more ergonomic for these specific needs.