ladybird/Ladybird
Ali Mohammad Pur 57714fbb38 RequestServer: Handle IPC requests on multiple threads concurrently
Previously RS handled all the requests in an event loop, leading to
issues with connections being started in the middle of other connections
being started (and potentially blowing up the stack), ultimately causing
requests to be delayed because of other requests.
This commit reworks the way we handle these (specifically starting
connections) by first serialising the requests, and then performing them
in multiple threads concurrently; which yields a significant loading
performance and reliability increase.
2024-05-20 08:03:35 +02:00
..
Android Meta+Documentation+Ports: Move from C++20 to C++23 2024-05-06 11:46:28 -06:00
AppKit Ladybird+LibWebView: Introduce a cache for cookies backed by SQL storage 2024-05-01 07:06:26 +02:00
cmake Ladybird: Add a simple TaskManager window for tracking child processes 2024-04-02 09:52:34 -06:00
Icons Ladybird/Qt: Introduce a hamburger menu and use by default 2024-05-06 08:24:56 -04:00
ImageDecoder Ladybird: Update Android build to work with current LibWebView/LibCore 2024-05-06 09:31:32 -06:00
Qt Ladybird: Ensure hamburger menu is placed within the browser window 2024-05-08 10:39:46 +02:00
RequestServer RequestServer: Handle IPC requests on multiple threads concurrently 2024-05-20 08:03:35 +02:00
SQLServer Ladybird: Register SQLServer with the task manager 2024-04-22 14:46:10 -06:00
WebContent Ladybird+LibWebView: Move SQLServer launcher to Ladybird 2024-04-22 14:46:10 -06:00
WebDriver Ladybird+Userland: Use ByteString for candidate server paths 2024-02-26 13:16:27 -07:00
WebWorker Ladybird+LibWebView: Move SQLServer launcher to Ladybird 2024-04-22 14:46:10 -06:00
.gitignore Ladybird: Add new template Kotlin Android application without Qt 2023-09-03 11:38:51 +02:00
CMakeLists.txt CMake: Resolve FIXMEs related to CMake < 3.20 2024-04-30 07:14:17 -06:00
default.nix nix: Clean up files, use good practices 2024-03-25 14:19:34 -06:00
FontPlugin.cpp Ladybird: Use Core::Resource to locate the emoji lookup path 2024-03-23 17:26:31 -04:00
FontPlugin.h LibWeb: Make FontPlugin::generic_font_name() return FlyString 2023-09-06 11:29:03 -04:00
HelperProcess.cpp Ladybird: Restore ability to run WebContent under callgrind 2024-04-27 15:17:31 +02:00
HelperProcess.h Ladybird+LibWebView: Move SQLServer launcher to Ladybird 2024-04-22 14:46:10 -06:00
ImageCodecPlugin.cpp LibWeb+WebContent: Convert ImageCodecPlugin to use the promise-based API 2024-04-23 12:32:04 -06:00
ImageCodecPlugin.h LibWeb+WebContent: Convert ImageCodecPlugin to use the promise-based API 2024-04-23 12:32:04 -06:00
Info.plist Ladybird: Register Ladybird as a browser-type application on macOS 2023-11-14 09:36:36 -05:00
MachPortServer.cpp LibCore+LibWebView: Move process statistics to LibCore 2024-04-22 14:46:10 -06:00
MachPortServer.h Ladybird+LibWebView: Add mechanism to get Mach task port for helpers 2024-04-09 16:43:27 -06:00
README.md Documentation: Update Ladybird README with more descriptive information 2024-04-23 11:24:14 -06:00
Types.h Ladybird: Use RequestServer for networking by default 2024-04-26 09:48:20 +02:00
Utilities.cpp Ladybird: Return a reference to the mach server name 2024-04-22 14:46:10 -06:00
Utilities.h Ladybird: Return a reference to the mach server name 2024-04-22 14:46:10 -06:00

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.