awesome-c VS SQLite

https://github.com/oz123/awesome-c#learning-reference-and-tu...

So, let’s go through an example. Since you’re used to using C, I’d suggest looking through the awesome-C repo. From there, you might decide you’re interested in graphics, so you check out OpenGL.

Awesome C - oz123

You can find a lot of resources at oz123 / awesome-c and this [https://www.linuxquestions.org/questions/programming-9/c-c-tutorials-825748/](C/C++ Tutorials thread).

For example, you can use the C language with sds strings (see https://github.com/antirez/sds) if you want to have an easier time with string formatting and don't want to worry about using the famously unsafe string.h functions correctly. You'll still program in ISO C, but just not in the standard library. The same applies to pretty much all parts of the standard library, the only part unsurpassed is pretty much just printf and the math headers (math.h, fenv.h, tgmath.h, complex.h) imo, and the occasional call to exit. A good place to look for libraries if you want to go that route is the awesome-c collection: https://github.com/oz123/awesome-c

There's an awesome C list of libraries and frameworks [1]. Pick one that suits your needs.

Time and again folks say such and such isn't suitable tool to do something. While some of those admonitions are true, if you're doing something to learn, feel free to ignore those and enjoy your learning. There're folks who learn assembly even today and learn a great deal of other things than assembly and have fun too.

As for C, it'd recommend most folks know the basics since many "modern" languages totally don't teach you those, and in fact hide the details from you that things feel like magic to you eventually if you keep using these high-level languages. This is okay as long as you can know the basics and map them back when needed.

[1]: https://github.com/oz123/awesome-c

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