FactGraph VS dali

I used to have a project like this. I was going to call it FactGraph: https://github.com/FactGraph/FactGraph/wiki

My idea was to build up a big community-maintained database containing facts and evidence, where everything is linked into a huge network. Everything would have a weight (sometimes automatically calculated from parent nodes), and the software would calculate probabilities for some big questions. Every user could also build their own personalized graph to explore their own worldview, and maybe even uncover some cognitive dissonance that they weren't aware of. Or you could use it to compare and contrast different philosophies, religions. Could even calculate a "coherence score" for each religion and denomination after crunching all of the available evidence.

Then I discovered RootClaim: https://www.rootclaim.com

They're doing something very similar, with a more targeted approach where they focus on some specific questions. e.g. COVID-19: https://www.rootclaim.com/analysis/what-is-the-source-of-cov...

RootClaim really seems to be nailing it so far, and hopefully they can continue to grow and become something like the project I was imagining.

Tangentially related, I've written a barebones assembler for Android .apk files once (strictly speaking, the assembler is for .dex files, but it also comes with a set of tools to package and sign .apk files). It's written mainly in Nim and provides enough primitives to allow creating Java "stubs" for native .so libraries, so that .apk-s can be built in Nim WITHOUT JDK AT ALL. The Android NDK is still kinda needed/useful, though IIRC mainly for access to adb, and especially adb logcat (which you'll need A LOT for debugging if you try to use this contraption).

I'd love to One Day™ Rewrite It In Rust.

The .dex assembler itself is at: https://github.com/akavel/dali — you may like to check out the tests at: https://github.com/akavel/dali/tree/master/tests to see how using it looks like.

An example project with a simple .apk written purely in Nim (NO JDK) is at: https://github.com/akavel/hellomello/tree/flappy (unfortunately, given Nim's poor packaging story, it's most probably already bitrotten to the extent that it can't be quickly and easily built & used out of the box). I recorded a presentation about this for an online Nim conference — see: https://www.youtube.com/watch?v=wr9X5NCwPlI&list=PLxLdEZg8DR...

https://github.com/akavel/dali was one (a fully hand-written assembler for Android .apk files); I managed to write a rudimentary flappy-bird-like prototype in it and did a presentation: https://www.youtube.com/watch?v=wr9X5NCwPlI&list=PLxLdEZg8DR... but on shelf now, didn't get much attention, and I don't feel bad about it. Had some roadblocks, but managed to overcome them, and I'm honestly surprised how the core effort was basically easy to implement and how the formats were open and relatively simple. (The main real issues I had were that debugging via adb logs was tiresome when something was not working.) What was funny about this project was that I started it with basically a thought of: "there will be probably some annoying roadblock at some point that will make it unviable to continue; I accept that and will be ok with stopping once I stumble upon it; but I don't see one clearly from the start [I did some quick initial research how the formats & the bytecode look and they seemed rather simple], and I'm really curious how far I can get if I decide to not think about this possible roadblock". Turns out I was able to get all the way to the end :D