limine VS SQLite

I assume this person meant to say `Limine'.

It's what I use for dualbooting Windows and Linux. It's really easy to Install, Use & Understand.

https://limine-bootloader.org/

They also publish a PHILOSOPHY.md page in their MS-source-git (github) that is, which is clearly offensive to us and many linux users:

I'm using Limine for bootloader, and in its documentation, in the Protocol page, we have:

Hello! While reading the Limine protocol specification i noticed that it says that "all non-usable entries (including kernel/modules) are not guaranteed any alignment, nor is it guaranteed that they do not overlap other entries". How am I supposed to get the memory size then? If the memory map entries can overlap, then summing their lengths won't work. Any help is appreciated, thanks in advance.

That's the Limine bootloader

It's way easier to use a pre-existing bootloader. I recommend Limine. It has it's own boot protocol that's designed for x86_64. You don't need any additional setup as it's already booted to long mode unlike Multiboot which needs you to switch to long mode since it's booted in protected mode. You can find an example kernel here.

It uses Limine as the Bootloader but I used Ponchos OS Dev Playlist as a base.

If you are into alternative storage engines for SQLite, there is also an LSM (Log-Structured Merge-tree) extension in the main repository that is not announced nor documented but seems to work. It’s based on the SQLite 4 project.

https://github.com/sqlite/sqlite/tree/master/ext/lsm1

https://www.charlesleifer.com/blog/lsm-key-value-storage-in-...

The sqlite code base is really well done. Lots of documentation.

https://github.com/sqlite/sqlite

Especially the VM part: https://github.com/spandanb/learndb-py/blob/master/learndb/v...

Compare it with this: https://github.com/sqlite/sqlite/blob/master/src/vdbe.c

That's said, I'm curious how complete this LearnDB is. SQLite is hard to read not only it's old but also it covers a lot of SQL and following SQL spec makes hings complicated. SQLite has great test suite so it's nice if you run the suit against this implementation.

Correct, see the github mirror[1]. I don't know how well supported that feature is compared to main branch. If it was completely stable, then it would have already landed in the main stable branch. Clarity about the roadmap of that branch would be nice.

1. https://github.com/sqlite/sqlite/tree/begin-concurrent

Including comprehensive comments, documentation and tests in a codebase takes time and effort.

Failing to do so creates code that is very difficult to maintain or for someone new to the codebase to understand.

However, time and effort may not be what the organization wants to pay for, and individuals may view their own incomprehensible code as something like job security, as they can't be replaced by someone else easily.

As an example of complicated code that's still well-documented, the open-source sqlite code is a good example, about 1/4 of the B-tree file is comments, every time a variable is defined there's a short note explaining what it's used for, every function has a comment header that's comprehensive, such that someone new to the codebase could construct a map of how it all works fairly quickly. It's a good model for how to avoid the problem:

https://github.com/sqlite/sqlite/blob/master/src/btree.c