SpacetimeDB VS sui

I don't use Rust for game dev but I do for low level libraries and find it easier than C++ to get started. I have enjoyed it more than Java and like it for different reasons than Go, but it feels good to program in.

As for the design patterns that a complex game requires, if you are considering Rust for game dev and ecs design patterns it might be useful to check out projects that are Rust centric like https://spacetimedb.com/.

Yeah, I worked on https://tablam.org and https://spacetimedb.com.

It becomes pretty clear that `order` is a significant property to make useful (and performant!) programs. "Duplicates" is also required to make usefull programs.

One nonobvious reason for this: You wanna report that a `customer` has a duplicated key `1`. If you CAN'T model `[(customer.id = 1), (customer.id = 1)]` then you can't report errors! And `erroneous` data is VITAL to make useful programs because then the only possibility is "perfect" data, and that is not possible!

Another reason is that we want to `count` duplicates, to see `duplicates`, and other NON-obvious at first: "What is a duplicate?". Get fun with floats, Unicode, combining case and non-case sensitive input... and is obvious that for useful programs IS REQUIRED to support bags in an extended version of the relational model.

And yet...

IS very important to remember about `set semantics` and try to adhere to it when makes sense. Your query planner will like it. You "valid" constraints like it. And `unique index` like it. And so on...

> I asked was about querying data without ever using a SQL language, like tapping directly into the data.

I agree (making https://tablam.org to try a fix & working on https://github.com/clockworklabs/SpacetimeDB in the SQL conformance).

Before I think SQL was bad. *Now I'm certain*. SQL is absurdly massive for things that could have collapse all the features 10x or more.

However, working in an RDBM now I also understand why is not desirable to make "raw" calls to the DB: The engine MUST mediate all the calls to make things works (from query optimization, execution, iteration, lock management, transaction management, etc).

Is incredible how much sophistication is in a simple `SELECT * FROM table`.

What I wish is to build a `Wasm-like` IR so that is what anybody target, and `SQL` is not the mediator.

I wouldn't ordinarily chirp about this because it seems to be such a common typo/mistake but the fact you have a badge for it <https://github.com/clockworklabs/SpacetimeDB/blob/0f1fdf62d0...> as well as typoing it down in the license section <https://github.com/clockworklabs/SpacetimeDB/blob/0f1fdf62d0...> makes it worth pointing out in hopes of correction

The SPDX for BUsiness Source License is BUSL https://spdx.org/licenses/BUSL-1.1.html but the SPDX for Boost Source License is BSL https://spdx.org/licenses/BSL-1.0.html

Based on a search <https://shields.io/search?q=license> it seems you're using the custom badge syntax <https://shields.io/badges/static-badge> so you have influence over the correction

Sui — a smart contract platform based on Narwhal and Bullshark protocols (written in Rust);

How can I avoid repeating these? [dependencies] sui-json = { git = "https://github.com/MystenLabs/sui.git", tag = "testnet-v1.5.0"} sui-sdk = { git = "https://github.com/MystenLabs/sui.git", tag = "testnet-v1.5.0"} sui-keys = { git = "https://github.com/MystenLabs/sui.git", tag = "testnet-v1.5.0"} sui-json-rpc-types = { git = "https://github.com/MystenLabs/sui.git", tag = "testnet-v1.5.0"} sui-types = { git = "https://github.com/MystenLabs/sui.git", tag = "testnet-v1.5.0"} shared-crypto = { git = "https://github.com/MystenLabs/sui.git", tag = "testnet-v1.5.0"}

Hello u/fancy_joe, It was moved from the framework. You can now find it as an example here. You will have to publish it to use it.

the command I'm running is "cargo install --locked --git https://github.com/MystenLabs/sui.git --branch devnet sui"

Sui's Tokenomics White Paper

Update 0.12.2 released on devnet. Detailed information on the link https://github.com/MystenLabs/sui/releases/tag/devnet-0.12.2.

We’ve recently made updates to our Wallet Adapter (Connect your dApps to Wallets on Sui) https://github.com/MystenLabs/sui/tree/main/sdk/wallet-adapter and Wallet Standard (browser wallet standard created in collaboration with Solana) https://github.com/MystenLabs/sui/tree/main/sdk/wallet-adapter/packages/wallet-standard. Note that these implementations are still new and will go through continual improvements and changes. As always we welcome contributors!! If you are building a non-browser wallet, please reach out–we are eager to engage with you to explore how to best integrate non-browser wallets into the wallet adapter ecosystem. Thanks all.

Github: https://github.com/MystenLabs/sui