I'm now trying to write a blog post and a script for a video on all of this, so I can share this journey with you. Let's see if I can release it on schedule, next Tuesday! If not, hopefully you can understand why. 😅

You can follow the development on this link, if you're interested. I created a GitHub Org, that is separate from my main account, because I invited a buddy of mine, who is a web dev guru, to work on the frontend. github.com/IllumiKnowLa...

Anyway, the day for Rust will come, but I need a reason. Maybe a tiny search engine, to use what I learned during my PhD? Who knows, still a recovering academic (this one I stole from the DuckDB team—too good not to).

I was on the fence on whether to go with Go or to go with Rust, but then I thought... Since I need to go, let's go with Go. I still have time to Rust (ironical name, since that language produces everything but rust). I must praise uv, just, and even zed! If it's built in Rust, it's built for speed!

I spend so many years doing Python, with a side of R, a dose of Java and Scala backends, and a slice of web UIs and visualizations in JS. I used to spend my days learning new languages, but then I started spending more time writing code than learning to code. So I missed it dearly!

I also started going deeper into Go and I'm having a blast learning a new language after so many years focused on other languages. I admit I'm slightly obsessed with Go now!

I was wrong, documentation is still available here: kuzudb.github.io/docs/

Not a sponsor, but I wouldn't mind! *wink* *wink* /cc @zed.dev

And to change batteries on time, especially when they’re getting direct warnings from the manufacturer.

At this point, I'm starting to question the decision to go with GitLab in such a resource constrained scenario. It's unclear what the problem is though, as I think 2 cores and 6 GiB RAM should be enough for a single user. Considering Gitea as an alternative, if this keeps happening.