oot VS SQLite

https://github.com/zeldaret/oot 100% Ocarina of Time is fully decomped, surprised we haven't seen any developments on Mario here. Also liboot is possible.

Here's the page from the Zelda "Reverse Engineer" GitHub wiki: https://github.com/zeldaret/oot/wiki/Getting-Started

well it is possible to crack a game without the source. in fact, it's possible to decompile source from the binary itself. This has been done with Mario64 and ocarina of time.

That being said, there is a lot of documentation out there on Ocarina of Time specifically. There's even a work-in-progress decompilation. You're going to have to learn a lot to get to the level where you can do the stuff you're wanting to do, but that's part of why you have to try to start smaller. You can even work on Ocarina of Time still, but start by picking a concrete goal and trying to hack it into the game. Build a tool from scratch that replaces text in the game, for example.

Mario 64 and Ocarina of Time were only just decompiled within the last couple of years. Jak and Daxter 1 was decompiled a few months ago. GTA 3 and Vice City have nearly finished decompilations, but TakeTwo took legal action against the developers before they put the finishing touches.

That said, I did my research before talking about source ports made from restoring the (nearly) original code using the compiled data and symbols). That's how SM64 and OoT (as well as other Zeldas in progress) were/are decompiled.

I've watched the video and I'm still convinced it provides false information. What is my source? The official OoT decompilation project: https://github.com/zeldaret/oot

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