ruffle VS tikv

shrug It finds its uses. It's just not that overstated.

sandspiel is quite popular and is built using WASM: https://sandspiel.club/

Google Earth - https://blog.chromium.org/2019/06/webassembly-brings-google-...

Ruffle (the "make Flash run safely" tool) - https://ruffle.rs/

Ableton's Learning Synths - https://learningsynths.ableton.com/

etc etc. It's just hard to tell when something is using WASM when it "just works" and is indistinguishable from optimized JavaScript

Out of curiosity a couple months ago I wondered if I could play my old Proximity flash game on Newgrounds from the browser within the Quest 3 VR headset, and it worked great!

That led me to do a little searching, and I discovered that originally the game didn't work in Ruffle, as I apparently did something with the play game button that wasn't normal. But someone put a fix in it back in 2020[1] in order to get my game working again. That was pretty neat. Felt kind of nice that people still cared enough about my old game to make sure it still works in an emulator.

Still working on a more in-depth sequel (using Monogame), and I'm way overdue to make a new web version of the original. Might knock that out once I get closer to getting the sequel out there.

[1]: https://github.com/ruffle-rs/ruffle/pull/1024

The sponsors section for the open source project they are using is a trip down flash game memory lane: https://github.com/ruffle-rs/ruffle/?tab=readme-ov-file#spon...

It is Flash! You're playing it with the free and open-source Flash clone Ruffle.

This is all using a really cool Flash emulator called https://github.com/ruffle-rs/ruffle

A relevant GitHub issue: https://github.com/ruffle-rs/ruffle/issues/325

Seems like being able to override was the plan, but not clear it was actually done?

I couldn't find any easily available official notice, but they seem to be using Ruffle[0]

[0] https://ruffle.rs/

TiKV is basically a layer on top of rocksdb https://github.com/tikv/tikv/blob/956610725039835557e7516828...

> Many,many smart people…

If you look inside the code you can see the stated features are a result of underlying engine (TiKV [0] also in c and rust from pingcap). Surrealdb is standing on shoulders of giants at present, they are TiKV, FoundationDB and rocksdb. The feature set they mentioned mostly coming from TiKV at present.

[0] https://tikv.org/

Hi Diggsey, great question. We are currently focussed on functionality and stability, and then will draw our attention to performance. Coming this week we have a RocksDB storage implementation. We've only just launched our initial beta version, and we know there is a lot of improvement and work to be done (some of these performance issues we know about already and are on our Github issues list).

With regards to the consistency/isolation model, SurrealDB sits on top of a number of key-value stores. By using the distributed highly-available TiKV storage backend, https://tikv.org, (and we have a FoundationDB integration in the works), the database is designed to be highly-scalable and highly-available. The same guarantees (albeit just single-node, so no high-availability or scalability) will be available with the RocksDB implementation coming this week. By sitting on top of these key-value stores, SurrealDB ensures that all transactions are ACID compliant. We don't want to go for speed (for instance by writing to /dev/null) over anything, but want SurrealDB to be a reliable and performant backend for any application. Obviously we have a way to go to catch up with PostgreSQL (launched in 1996), but we will strive to get there!

If you are looking for a production ready distributed store written in Rust. Check out TiKV(https://github.com/tikv/tikv), which was also mentioned in the acknowledge section of the project's README.

There's also a full-featured distributed RDBMS called TiDB built on top of TiKV.

Fair enough. Indeed I didn't consider support costs. Thank you for your answer!

Actually let me ask another thing. Your FAQ mentions you're considering hosting CockroachDB as a drop-in distributed replacement for PostgreSQL [0], and also you currently offer a distributed, eventually consistent PostgreSQL replication solution [1].

Is either Tikv [2] (distributed key-value store) or Tidb [3] (distributed database with a mysql interface, built on top of Tikv) on your radar?

You already offer Redis as a key-value store, but Tikv has an amazing property: it ensures strong consistency globally (not eventual consistency). Tidb, being built on top of Tikv, also has strong consistency.

[0] https://fly.io/blog/fly-answers-questions/#q-what-is-fly-doi...

[1] https://fly.io/blog/globally-distributed-postgres/

[2] https://github.com/tikv/tikv

[3] https://github.com/pingcap/tidb

tikv — A distributed KV database in Rust

TiKV: basis data key-value transaksional yang terdistribusi.