Ladybird is a full-featured web browser engine implemented primarily in C++ with Rust components for performance-critical tasks. It includes its own JavaScript engine (LibJS) with bytecode interpreter and JIT compiler (Flap), a rendering engine (LibWeb) that implements HTML, CSS, DOM, SVG, WebGL, WebAudio, and many other web standards, a graphics library (LibGfx) with Skia integration, a media pipeline (LibMedia) supporting audio/video decoding via FFmpeg, and a custom garbage collector (LibGC). The architecture is multi-process: separate processes for UI, web content, image decoding, networking, and compositing, communicating via a custom IPC framework (LibIPC). The codebase is actively developed with a strong focus on web standards compliance, evidenced by extensive test suites including imported Web Platform Tests (WPT). It is not a data research project; it is a production-quality browser engine designed for the Ladybird browser, with cross-platform support for Linux, macOS, and Android.
Servo is a parallel web browser engine written in Rust, designed to leverage modern hardware capabilities for rendering and script execution. The codebase is structured as a large Rust workspace with distinct components for scripting, layout, networking, styling, and media handling. The primary entry point is the 'servoshell' port, which acts as the browser host application. The repository includes extensive Web Platform Tests (WPT) to ensure standards compliance, alongside a custom Python-based build and test infrastructure ('mach'). While the core engine is tightly coupled, several tooling components and specific subsystems (like storage and bindings) exhibit reusable architectural patterns. The project demonstrates high engineering craftsmanship in memory safety and parallelism, utilizing Rust's ownership model to prevent data races in the rendering pipeline. However, the sheer scale of the test suite (Web Platform Tests) and the reliance on auto-generated test files introduce significant maintenance complexity. The codebase maintains its own forks of core libraries (e.g., 'stylo', 'servo_arc'), which creates a medium risk of technical drift if upstream changes are not synchronized. The build system and test infrastructure are robust but complex, requiring specific tooling to reproduce builds across platforms.