ClassiCube is a cross-platform voxel-based sandbox game engine inspired by Minecraft Classic. It features a modular architecture with clear separation of concerns between rendering, input, audio, networking, world management, and game logic systems. The engine supports an extensive range of platforms from modern desktop and mobile systems to legacy consoles like PS1, PS2, Dreamcast, GBA, and many others through platform-specific implementations behind common abstractions. Key features include block placement/breaking, inventory management, chat system, texture packs, lighting (classic and fancy modes), entity rendering, and multiplayer networking.
This repository is the official HashiCorp Terraform provider for Microsoft Azure (azurerm). It enables declarative management of Azure infrastructure—resources, data sources, and services—through Terraform configurations. The provider is written in Go and uses the Terraform Plugin SDK and Plugin Framework to implement CRUD operations, state migrations, custom polling for asynchronous operations, and extensive input validation. Its architecture follows a modular service registration pattern: each Azure service (e.g., compute, network, storage, appservice) is self-contained within `internal/services/<service>/`, with its own client construction, resource definitions, validation functions, and acceptance tests. Key entry points include `main.go` for provider initialization, `internal/provider/provider.go` for resource registration, and `internal/services/*/registration.go` for service wiring. Data flows from Terraform configuration through the provider's SDK layer to Azure REST APIs via the `go-azure-sdk` library. The codebase is large (43k+ files) but well-organized, with extensive test coverage and tooling for documentation linting, schema API compatibility checks, and PR guide suggestions. It is actively maintained with frequent releases and a large community (5k+ stars, 5k+ forks).
The Dependency Injector is a mature, feature-rich dependency injection framework for Python. It provides core DI patterns through providers (Factory, Singleton, Resource, etc.), containers (Declarative/Dynamic), and wiring mechanisms (@inject decorator). The framework emphasizes explicit dependency declaration, testability, and loose coupling while supporting async/await, configuration management from multiple sources, and runtime provider overriding. It includes framework-specific integrations (Flask, Django, FastAPI, etc.) via its wiring module and extension system, though the core remains framework-agnostic. Architecturally, the codebase separates concerns into distinct modules: providers handle object creation/lifecycle, containers manage provider resolution and hierarchy, wiring enables automatic dependency injection into functions/methods, resources manage lifecycle-dependent objects (e.g., DB connections), and configuration providers unify settings from YAML/INI/JSON/env. The framework uses Cython for performance-critical components while maintaining a pure Python interface. Comprehensive documentation, extensive test suite, and numerous examples demonstrate practical integration patterns across web applications, daemons, and cloud services. The project shows strong maintenance with frequent releases, active issue triage, and broad Python version support (3.8-3.14). Technical drift is low due to proactive dependency updates, removal of deprecated Python versions, and adherence to modern Python practices. The codebase exhibits high craftsmanship in its provider patterns, particularly the Resource provider's context-manager semantics and the wiring module's automatic dependency resolution, making it a reusable dependency injection solution for Python applications.
Rustler is a Rust library for writing safe, efficient Native Implemented Functions (NIFs) for the Erlang VM (BEAM), primarily used from Elixir. It provides a high-level, type-safe API that abstracts away the low-level C NIF interface, allowing developers to write NIFs in idiomatic Rust with automatic encoding/decoding of Erlang terms. The architecture consists of three main crates: `rustler` (core runtime and type system), `rustler_codegen` (procedural macros for NIF export and derive traits), and `rustler_mix` (Elixir Mix integration for building and loading NIFs). Key entry points include the `init!` macro to register NIFs, the `#[nif]` attribute macro to define functions, and derive macros like `NifStruct`, `NifMap`, and `NifTaggedEnum` for automatic term conversion. Data flows involve Rust functions receiving decoded Erlang terms (via the `Decoder` trait) and returning encoded terms (via the `Encoder` trait), with support for complex types, resources, threading, and serde serialization. External dependencies include the Erlang/OTP NIF API (dynamically loaded), the `inventory` crate for static registration, and optional `serde` and `num-bigint` crates.
STC (Smart Template Containers) is a mature, type-safe generic container and algorithm library for C99/C11. It is not an application or service; it is a library component that developers link into systems programs, embedded code, games, and simulations. The library provides macro-instantiated generic containers (vec, list, deque, stack, queue, priority queue, hash map, hash set, sorted map, sorted set, bitset), string types with small-string optimization (cstr, csview), multi-dimensional array views (cspan), smart pointers (box, arc, rc), a regular expression engine (cregex), a stackful coroutine framework, random number generators, and algorithms such as sorting, filtering, and binary search. The code implements the actual functionality; the README and docs describe usage, but the headers and src tree are the ground truth. The architecture is a hybrid header-only and compiled library. Templated containers are generated at compile time by a sophisticated macro trait system (via i_key, i_type, c_pro_key, etc.), while non-templated facilities like cstr, cregex, cspan, and random are partially implemented in src/ and linked as libstc. Public entry points are the headers under include/stc/; the build supports both Makefile and Meson, with examples and tests under examples/ and tests/. External dependencies are minimal, essentially the C11 standard library only, with compiler-specific pragmas and intrinsics for GCC, Clang, MSVC, and TCC. Data flows are primarily in-memory: containers own and manage elements, string operations transform UTF-8 text, regex compiles and executes NFA graph matching, and coroutines yield and resume across tasks. The codebase demonstrates strong engineering practice: a custom test harness (ctest.h), CI with sanitizers across three OSes, extensive API documentation, and a large examples corpus. The macro-based generic system is clever and powerful but carries the usual debugging and tooling complexity; deprecated aliases still exist from API churn. Overall this is a high-quality, reusable C library with several notably self-contained subsystems that could be lifted into other projects.
This is a small, focused Go library that automatically sets the GOMEMLIMIT environment variable for Go applications based on the Linux cgroup memory limit. It provides a simple side-effect import (import _ "github.com/KimMachineGun/automemlimit") that configures the Go runtime memory limit to a configurable fraction (default 90%) of the cgroup limit, or alternatively offers a programmatic API via memlimit.Set() with options for custom providers, ratios, minimum limits, and periodic refresh. The library handles both cgroup v1 and v2, correctly resolving the effective memory limit from the cgroup hierarchy, including handling of conflicting mounts, unlimited memory sentinels, and fallback to system memory. It is not a hybrid; it is purely an application library.
MethaneKit is a cross-platform graphics rendering framework that provides abstractions over DirectX 12, Vulkan, and Metal APIs. It features a layered architecture with platform-independent interfaces (RHI), platform-specific implementations, an application framework, UI components, and mathematical utilities. The framework includes tutorial applications demonstrating various graphics techniques from basic triangle rendering to compute shaders and parallel rendering. Key systems include resource management, command submission, pipeline state handling, and synchronization primitives. The codebase demonstrates modern C++ practices with extensive use of templates, PIMPL idiom, and interface-based design.
RocksDict is a persistent key-value store for Python, backed by the RocksDB embedded database. It provides a Pythonic dictionary-like interface (`Rdict`) for storing and retrieving data that exceeds memory capacity, with support for arbitrary Python objects via pickle or raw bytes. The system is implemented as a Rust extension (using PyO3/maturin) that interacts with the RocksDB C++ library via FFI, offering high performance and durability. The architecture separates concerns into a safe Rust core and a thin Python binding layer. The Rust core implements resource management (via `DbReferenceHolder` to handle RocksDB reference counts and background work cleanup), centralized FFI error handling (through the `ffi_try` macro), and a flexible encoding layer (`encoder.rs`) that supports both raw bytes and pickled Python objects with type tags for efficient deserialization. Configuration persistence is handled via `RocksDictConfig`, which serializes database options to JSON for automatic reloading, enabling seamless recovery of tuned settings. Key features include column families, snapshots, write batches, checkpoints, and SST file ingestion, making it suitable for a wide range of applications from caching to large-scale data storage. The project is actively maintained with comprehensive CI coverage across multiple Python versions and platforms, demonstrating a commitment to reliability and cross-platform compatibility.
The Doomsday Engine is a modular game engine and source port for classic FPS games (Doom, Heretic, Hexen, Doom64) with client-server architecture. It provides enhanced rendering (OpenGL), audio systems, GUI frameworks, networking, and scripting capabilities. The engine supports extensibility via plugins and includes tools like Amethyst for documentation processing. The codebase shows strong separation of concerns with distinct libraries for core functionality, game logic, rendering, and UI. While actively maintained, it exhibits technical drift due to platform-specific conditionals, legacy code sections, and complex dependency management.
This repository is a curated, actively-maintained personal knowledge base of academic paper reading notes, focused on systems for machine learning, cloud computing, and related areas. It is organized by conference venue (e.g., OSDI, SOSP, MLSys) and by topic (e.g., LLM systems, GPU sharing, memory disaggregation). The core content consists of markdown files with structured summaries (TL;DR, background, design, evaluation) and cross-linked topic aggregation pages. The repository is the source for a GitBook static site and includes scripts for building and serving that site, as well as utilities for PDF text extraction. While not a data pipeline or software application, it functions as a high-quality research resource with consistent formatting, curation guidelines, and reusable templates for note-taking and paper list organization.
This repository is a reimplementation of the Deus Ex: Human Revolution Director's Cut (DXHRDC) game engine, created through manual decompilation and cleanup of the original binary, supplemented with debug information from a leaked Tomb Raider (2013) build (same engine family). It is not a matching decompilation and lacks automated resynchronization with the original binary. The engine requires original game assets (BIGFILE.* files) to run and provides core systems for rendering (DirectX 11 abstraction), audio (FMOD-based), animation (animation graph), game logic (object management, AI, player systems), input, UI (Scaleform via ImGui), resource management, and world streaming. The architecture is modular but monolithic, with a central game loop in cdcGameShell/MainG2.cpp. While the code shows evidence of structured design (interfaces, resource management, job system), it contains numerous TODOs, HACKs, and incomplete implementations, indicating ongoing work. Dependencies include DirectX 11 (or dxvk-native for Linux), FMOD, Dear ImGui, and miniz. The project is actively maintained with recent commits.