For example, consider the following IPC message: do_something(u64 page_id, String string, Vector<Data> data) =| We would previously generate the following C++ method to encode/transfer this message: void do_something(u64 page_id, String string, Vector<Data> data); This required the caller to either have to copy the non-trivial types or `move` them in. In some places, this meant we had to construct temporary vectors just to send an IPC. This isn't necessary because we weren't holding onto these parameters anyways. We would construct an IPC::Message subclass with them (which does require owning types), but then immediate encode the message to an IPC::MessageBuffer and send it. We now generate code such that we don't need to construct a Message. We can simply encode the parameters directly without needing ownership. This allows us to take view-types to IPC parameters. So the above example now becomes: void do_something(u64, StringView, ReadonlySpan<Data>); |
||
---|---|---|
.devcontainer | ||
.github | ||
AK | ||
Base/res | ||
Documentation | ||
Libraries | ||
Meta | ||
Services | ||
Tests | ||
Toolchain | ||
UI | ||
Utilities | ||
.clang-format | ||
.clang-tidy | ||
.clangd | ||
.editorconfig | ||
.gitattributes | ||
.gitignore | ||
.gn | ||
.mailmap | ||
.pre-commit-config.yaml | ||
.prettierignore | ||
.prettierrc | ||
.swift-format | ||
.ycm_extra_conf.py | ||
CMakeLists.txt | ||
CMakePresets.json | ||
CODE_OF_CONDUCT.md | ||
CONTRIBUTING.md | ||
flake.lock | ||
flake.nix | ||
ISSUES.md | ||
LICENSE | ||
README.md | ||
SECURITY.md | ||
shell.nix | ||
vcpkg-configuration.json | ||
vcpkg.json |
Ladybird
Ladybird is a truly independent web browser, using a novel engine based on web standards.
Important
Ladybird is in a pre-alpha state, and only suitable for use by developers
Features
We aim to build a complete, usable browser for the modern web.
Ladybird uses a multi-process architecture with a main UI process, several WebContent renderer processes, an ImageDecoder process, and a RequestServer process.
Image decoding and network connections are done out of process to be more robust against malicious content. Each tab has its own renderer process, which is sandboxed from the rest of the system.
At the moment, many core library support components are inherited from SerenityOS:
- LibWeb: Web rendering engine
- LibJS: JavaScript engine
- LibWasm: WebAssembly implementation
- LibCrypto/LibTLS: Cryptography primitives and Transport Layer Security
- LibHTTP: HTTP/1.1 client
- LibGfx: 2D Graphics Library, Image Decoding and Rendering
- LibUnicode: Unicode and locale support
- LibMedia: Audio and video playback
- LibCore: Event loop, OS abstraction layer
- LibIPC: Inter-process communication
How do I build and run this?
See build instructions for information on how to build Ladybird.
Ladybird runs on Linux, macOS, Windows (with WSL2), and many other *Nixes.
How do I read the documentation?
Code-related documentation can be found in the documentation folder.
Get in touch and participate!
Join our Discord server to participate in development discussion.
Please read Getting started contributing if you plan to contribute to Ladybird for the first time.
Before opening an issue, please see the issue policy and the detailed issue-reporting guidelines.
The full contribution guidelines can be found in CONTRIBUTING.md
.
License
Ladybird is licensed under a 2-clause BSD license.