servo-embedding-example VS RethinkDB

Projects that tried to make servo embeddable are all dead and gone (see https://github.com/paulrouget/servo-embedding-example for example)

So yeah last time I tried to use gecko I failed and didn't try again (years ago) nobody is willing to do the work and mozilla seems to focus more on other stuff...

The problem is that embedding servo is not that easy. This is the only info I found on it:

https://github.com/paulrouget/servo-embedding-example

And it is a 4-year old example.

This, from the same author, is also abandoned: https://github.com/paulrouget/servo-embedding-api

https://github.com/servo/servo/issues/18479

I don't think that embedding is their focus at all, although it does sound like a killer feature to keep the project alive.

No, not yet. But Servo can be used headless:

https://github.com/paulrouget/servo-embedding-example

I've been poking around, testing and breaking database servers for a long time (more than 20 years today). But a few years ago I came across a jewel, the grail, one of the best solutions available. Under the radar, shunned for whatever reason, RethinkDB is nonetheless one of the finest database server projects I've ever tested.

RethinkDB[0] looks like a "too good to be true" type of database. Anyone using it in production? What is your experience like? What are the pros and cons?

[0] https://rethinkdb.com

Since you’re not new to the field you might want to peek https://rethinkdb.com/ since it got picked up as an open source project.

No I don't think that's relevant. They implement their own btree it seems [0].

They don't use a key-value store library.

I know it's a bit of a fine line. But I'm talking about standalone libraries people embed across different applications/databases. That's what RocksDB/LevelDB/Pebble are.

[0] https://github.com/rethinkdb/rethinkdb/tree/v2.4.x/src/btree

A Data Objects represents data which can be saved inside a database. This concept is in the heart of SQLAlchemy, but as the name should be obvious: it's for SQL Database (in general). Today, there are now document databases too (like MongoDB, ArangoDB, RethinkDB that I love so much, or even PostgreSQL). So, a "data" is like a "structured and typed document" that you save "as is". That's not the same paradigm, not the same controls. There are advantages and disadvantages, but we won't debate that here.

There are multiple ways to share data between two (or more) instances of your app: - you can use a shared storage, such as Cloud Firestore, - you can build your own backend (based on a real-time database, such as RethinkDB), - or you can rely on local communication using the Multipeer framework you linked.