Home

Awesome

Lexbor: Crafting a Browser Engine with Simplicity and Flexibility

Why build yet another browser engine? There's a myriad of challenges developers face in fully utilizing modern web technologies. Parsing HTML and CSS, dealing with URLs and encodings often involves slow, resource-heavy implementations or outdated solutions. Even established solutions, written in C++ and reaching tens of megabytes in volume, are often not versatile enough. Meanwhile, language-specific implementations for Python, Node.js, Rust, or any other favorite of the day are slow and prone to lock-in.

The Core Requirements

Lexbor's core requirements rose from the ashes of these challenges:

Portability

Lexbor aims to adapt to different platforms and integrate into various programming languages. It's not yet another library full of quirks and idiosyncrasies; Lexbor aims to offer developers flexibility to incorporate it into their work directly, regardless of the programming language they chose.

Modularity

Lexbor wants to keep things simple: Developers should be able to use only the parts they need. Whether it's an HTML or URL parser, the engine's code should be straightforward and easy to navigate, promoting rapid development.

Speed

In a nutshell, Lexbor wants things to happen real fast. It's not just about making a browser engine; it's about making sure that everything, even the most resource-intensive tasks such as HTML parsing, occur swiftly to meet the real-time demands of modern web applications.

Independence

Lexbor empowers developers by giving them full control over algorithms, resources, and dimensions. By eliminating on external dependencies, we let developers customize the engine without sacrificing performance or features.

Compliance

Lexbor commits to industry standards. Developers need to be sure that the code aligns with widely established specifications. The output of Lexbor's modules, be it HTML, CSS, URLs, or others, should match that of modern browsers, meeting industry specifications.

Origin Story

Having had all these goals in mind for about a decade, Alexander Borisov, whose name gave the project its title, came up with the idea of a browser engine crafted entirely in C (there's no school like the old school). The language was chosen simply because we believed it could meet all the criteria seamlessly.

Unlike heavyweights such as WebKit or Blink, Lexbor takes a lean and focused approach, delivering a nimble yet powerful browser engine. All it takes is years of top-notch developer expertise.

An important point to make: Lexbor doesn't stop at parsing and rendering modern HTML. It offers each component as a standalone entity, ready to be integrated into other people's projects. This approach sets us apart, providing a modular solution that not only meets browser needs but also empowers developers with versatile tools for their own web-related tasks.

All in all, we envision Lexbor a promising player in the menagerie of browser technologies, pushing the boundaries and helping developers fully leverage modern web technologies.

Features

HTML Module

CSS Module

Selectors Module

Encoding Module

URL Module

Punycode Module

Unicode Module

Development of modules in process

Build and Installation

Binary packages

Binaries are available for:

Currently for x86_64 architecture. If you need any other architecture, please, write to support@lexbor.com.

vcpkg

For vcpkg users there is a lexbor port that can be installed via vcpkg install lexbor or by adding it to dependencies section of your vcpkg.json file.

macOS

Homebrew

To install lexbor on macOS from Homebrew:

brew install lexbor

MacPorts

To install lexbor on macOS from MacPorts:

sudo port install lexbor

Source code

For building and installing Lexbor library from source code, use CMake (open-source, cross-platform build system).

cmake . -DLEXBOR_BUILD_TESTS=ON -DLEXBOR_BUILD_EXAMPLES=ON
make
make test

Please, see more information in documentation.

Single or separately

Single

Separately

You only need an HTML parser? Use liblexbor-html.

Separate modules may depend on each other. For example, dependencies for liblexbor-html: liblexbor-core, liblexbor-dom, liblexbor-tag, liblexbor-ns.

The liblexbor-html library already contains all the pointers to the required dependencies. Just include it in the assembly: gcc program.c -llexbor-html.

External Bindings and Wrappers

You can create a binding or wrapper for the lexbor and place the link here!

Documentation

Available on lexbor.com in Documentation section.

Roadmap

Please, see roadmap on lexbor.com.

Getting Help

SAST Tools

PVS-Studio - static analyzer for C, C++, C#, and Java code.

AUTHOR

Alexander Borisov borisov@lexbor.com

COPYRIGHT AND LICENSE

Lexbor.

Copyright 2018-2024 Alexander Borisov

Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at

   http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.

Please, see LICENSE file.