lexbor VS linux

It supports both CSS selectors and XPath like Nokogiri, but with separate engines - parsing and CSS engine by Lexbor, XPath engine by libxml2. (Nokogiri internally converts CSS selectors to XPath syntax, and uses XPath engine for all searches).

An HTML parser, probably the simplest relatively modern example I could find is 1MB https://github.com/lexbor/lexbor (haven't used it, but might look more into it now that I know it exists.)

Lazyweb link: https://github.com/rushter/selectolax

although I don't follow the need to have what appears to be two completely separate HTML parsing C libraries as dependencies; seeing this in the readme for Modest gives me the shivers because lxml has _seen some shit_

> Modest is a fast HTML renderer implemented as a pure C99 library with no outside dependencies.

although its other dep seems much more cognizant about the HTML5 standard, for whatever that's worth: https://github.com/lexbor/lexbor#lexbor

---

> It looks like the author of the article just googled some libraries for each language and didn't research the topic

Heh, oh, new to the Internet, are you? :-D

Lexbor is here: https://github.com/lexbor/lexbor

Well, regarding HTML5, what I've found was libxml (does not support tag-soup HTML5), https://github.com/lexbor/lexbor, for which I was unable to find good documentation ( see https://lexbor.com/docs/lexbor/#dom), Apache Xerces (appears to not support tag-soup HTML5 as well), and Gumbo, which does not appear to be active and to support selectors and XPath (although there are libraries that add that).

I think we've all (mostly?) tried it. It really is the Wild West of the web when you're trying to parse other people's HTML, though.

I've played around with this parser which is extremely quick. https://github.com/lexbor/lexbor

I’m glad to have the opportunity to contribute to an open-source project that is used by thousands of people. Hopefully, we will speed up Nokogiri (or XML parser it uses) to match the performance of html5ever or lexbor at some point in the future. 800 ms to extract data from HTML is still too much.

It’s all optional. Before I found the Linux kernel’s nolibc [0], I wrote a minimal C runtime based on bunch of stuff I read [1].

[0] https://github.com/torvalds/linux/tree/master/tools/include/...

[1] https://github.com/lpsantil/rt0/blob/master/src/lib/00_start...

As a data point, the Linux kernel has a long list of workarounds for "ata" related devices (SSDs, HDDs, etc):

https://github.com/torvalds/linux/blob/69f2c9346313ba3d3dfa4...

Can be a bit eye opening to look down that and see equipment you're using listed. ;)

This seems to be the same thing for NVMe. eg Samsung, SK Hynix, Micron, Kingston, ADATA, Intel drives:

https://github.com/torvalds/linux/blob/69f2c9346313ba3d3dfa4...

Not quite as easy to read and understand as the ata driver code though. :/

There are further device specific workarounds in other parts of the NVMe driver code too.

eg for specific Toshiba, LiteON, and Kioxia devices:

https://github.com/torvalds/linux/blob/69f2c9346313ba3d3dfa4...

While this eems to be special handling for Samsung X5 SSD external drives, and also Samsung 970 Evo Plus drives:

https://github.com/torvalds/linux/blob/69f2c9346313ba3d3dfa4...

Linux 18k contributors 146k stars

git clone https://github.com/torvalds/linux windows cd windows make menuconfig make -j$(nproc)

https://github.com/torvalds/linux/tree/master/drivers/usb/gadget/udc has a bunch of supported UDCs. The Steam Deck just seem to use the AMD's built-in USB controller (check with lspci), and I doubt it can support it.

See the link

The VT subsystem is not as well-maintained as other subsystems in the Linux kernel. Even Linus Torvalds, who wrote a large portion of the VT subsystem very early in Linux's history, considers it "bitrot" now. A few years ago CVE-2020-14390 was discovered in the VT subsystem, which was the VT console corrupting memory when scrolling up in some conditions. When this issue was discovered, the best fix that the kernel developers did to avoid making large changes to code they consider to be fragile, was to simply prevent scroll up from working in the VT console. The commit message in https://github.com/torvalds/linux/commit/973c096f6a85e5b5f2a295126ba6928d9a6afd45 provides further reference.