toltec VS oxide

3.x support will come to toltec, I've been blocked by stuff outside of my control a couple of times. Including things happening in my life that I won't get into.

You can see the current progress here: https://github.com/toltec-dev/toltec/issues/820

As for the comment on the kernel change, that was actually an ask by someone in the community: https://github.com/reMarkable/linux/issues/8

I love seeing work in this space! I made a collaborative whiteboard app for the reMarkable a while ago: https://github.com/fenollp/reMarkable-tools

It is packaged in the homebrew Toltec repo https://toltec-dev.org/

Remember to read the warning on Toltec home page:

- https://toltec-dev.org/

Do you ever plan to put your own tools and stuff on it? If so I would reccomened staying on 2.15 so you can use https://toltec-dev.org/. Also newest version 3 software forces infinite scroll and a lot of people absolutely hate it. I happily stay on 2.10. You can change versions as well, unofficially. Not sure if using the cloud still works with that, lots of us have cut that out entirely.

Definitely start by installing toltec if your device is on version <=2.15.1.1189, https://toltec-dev.org

Still waiting on ddvk-hacks and rm2fb. Only an updated rm2fb package is pending: https://github.com/toltec-dev/toltec/pull/656

Sorry about that, it's just a shortcut for https://github.com/fcoury/oxide.

Mostly on MongoDB to PostgreSQL translation server: http://oxidedb.com or https://demo.oxidedb.com.

I have been wanting to dive deep into a Rust project and the challenge of implementing the MongoDB protocol and then translating it into some sort of SQL counterpart was the first thing that really clicked and got me excited enough to get me working on it nonstop for 3 weeks now.

Some backstory:

I have created a product that relies on MongoDB for a document store but doesn’t really need any of the distributed features to really justify having a hosted MongoDB or DocumentDB instance. Now that we’re trying to turn this into a product, we’re seeing that some companies have a little bit of resistance around managing yet another database. Most of our clients already have and manage PostgreSQL in one form or another. I knew that PostgreSQL already offered first class JSON support, but I didn’t want to rewrite the application data layer from scratch if I could avoid it. That’s when I started researching if there was a “proxy” that would translate the MongoDB protocol - that I was completely ignorant about - into PostgreSQL. To my surprise there was nothing ready for production use but I found MangoDB that later on became FerretDB. I delved into the code and was in love with the idea. The team around is really nice, but I found that they had greater ambitions - they basically wanted to offer multiple backends, namely Tigris, on top of PostgreSQL.

On the other hand, I have been waiting to find an excuse to delve deeply into the rust ecosystem but never really found something I was passionate about until I had the idea of challenging myself to see if I could learn about the protocol that MongoDB uses by relying on their public documentation and the hints I found on FerretDB.

Another thing I added to my toolbelt while developing this was about creating parsers. In order to transform MongoDB JSON to SQL queries, I ported an existing library from the MongoDB team from PEG.js to pest.rs!

It’s in very early stages, and it’s work from someone that is not yet super comfortable with the stack so keep in mind this is the beginning of a journey for me that I embarked out of pure joy on getting a tiny bit better on rust and making things click internally.