398ae75f9a
Now that the chrome process is a singleton on all platforms, we can safely add a cache to the CookieJar to greatly speed up access. The way this works is we read all cookies upfront from the database. As cookies are updated by the web, we store a list of "dirty" cookies that need to be flushed to the database. We do that synchronization every 30 seconds and at shutdown. There's plenty of room for improvement here, some of which is marked with FIXMEs in the CookieJar. Before these changes, in a SQL database populated with 300 cookies, browsing to https://twinings.co.uk/ WebContent spent: 19,806ms waiting for a get-cookie response 505ms waiting for a set-cookie response With these changes, it spends: 24ms waiting for a get-cookie response 15ms waiting for a set-cookie response |
||
---|---|---|
.. | ||
Android | ||
AppKit | ||
cmake | ||
Icons | ||
ImageDecoder | ||
Qt | ||
RequestServer | ||
SQLServer | ||
WebContent | ||
WebDriver | ||
WebWorker | ||
.gitignore | ||
CMakeLists.txt | ||
default.nix | ||
FontPlugin.cpp | ||
FontPlugin.h | ||
HelperProcess.cpp | ||
HelperProcess.h | ||
ImageCodecPlugin.cpp | ||
ImageCodecPlugin.h | ||
Info.plist | ||
MachPortServer.cpp | ||
MachPortServer.h | ||
README.md | ||
Types.h | ||
Utilities.cpp | ||
Utilities.h |
Ladybird
Ladybird is a web browser built on the LibWeb and LibJS engines from SerenityOS. The Browser UI has a cross-platform GUI in Qt6 and a macOS-specific GUI in AppKit.
Ladybird aims to be a standards-compliant, independent web browser with no third-party dependencies. Currently, the only dependencies are UI frameworks like Qt6 and AppKit, and low-level platform-specific libraries like PulseAudio, CoreAudio and OpenGL.
Important
Ladybird is in a pre-alpha state, and only suitable for use by developers
Features
The Ladybird browser application uses a multiprocess architecture with a main UI process, several WebContent renderer processes, an ImageDecoder process, a RequestServer process, and a SQLServer process for holding cookies.
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.
All the core library support components are developed in the serenity monorepo:
- LibWeb: Web Rendering Engine
- LibJS: JavaScript Engine
- LibWasm: WebAssembly implementation
- LibCrypto/LibTLS: Cryptography primitives and Transport Layer Security (rather than OpenSSL)
- LibHTTP: HTTP/1.1 client
- LibGfx: 2D Graphics Library, Image Decoding and Rendering (rather than skia)
- LibArchive: Archive file format support (rather than libarchive, zlib)
- LibUnicode, LibLocale: Unicode and Locale support (rather than libicu)
- LibAudio, LibVideo: Audio and Video playback (rather than libav, ffmpeg)
- LibCore: Event Loop, OS Abstraction layer
- LibIPC: Inter-Process Communication
- ... and more!
Building and Development
See build instructions for information on how to build Ladybird.
See CONTRIBUTING.md for information on how to contribute to Ladybird.
More Information
For more information about the history of Ladybird, see this blog post.
The official website for Ladybird is ladybird.dev.