db VS openEtG

We actually did work on this a few years ago but did not get enough takers for it. We created a one size fits all database, that leverages the full capability of the file system.

Try it here: https://github.com/blobcity/db

PS: I am the chief architect of the DB, and the project is no longer being actively maintained by us. But if you make a contribution, we will oblige to review and merge a PR.

Bottom line, nothing you do can make your database faster than the filesystem. So why not make a database that just uses the filesystem to the fullest, than creating a filesystem on top of a filesystem. BlobCity DB does not create a secondary filesystem. It dumps all data directly to the filesystem, thereby giving peak filesystem performance. This is scientifically really the best it gets from a performance standpoint. Not necessarily the most efficient in data storage / data-compression standpoint.

This means, we gain speed, while compromising on data-compression. We produce a larger storage footprint, but are insanely fast. Storage is cheap, compute isn't. So that should be okay I suppose.

For an example of binsearch algo, I recently dipped into this while switching some code from floats to fixed point arithmetic (reducing overall wasm blob size)

https://github.com/serprex/openEtG/blob/2011007dec2616d1a24d...

This seems pretty low level. When I wanted async wasm execution (to run multithreaded game ai simulation or to run game ai outside of UI thread) I was able to go with WebWorkers: https://github.com/serprex/openEtG/blob/master/src/AiWorker....

Having the async at the WASM level would help avoid having overhead from serialize/deserialize between web workers. I wrote this years ago, so not sure what progress has been made for having the wasm module running multiple threads. On that front you may still be better off spawning multiple wasm modules

(( dunno which version you're trying, cuz there've been a lot of fan versions after the original went down, but this should be the one most people use ))

Check out the spiritual successor, openEtG: https://etg.dek.im

This one? https://etg.dek.im/

If you want a reference to a real code base, there's openEtG's handleget.rs

https://github.com/rustwasm/wasm-pack/pull/1089

Very straight forward changes. Emailed Ashley about helping, no response

Updates to wasm-bindgen shouldn't require a change to wasm-pack. It should expose ways to pass flags down & not have an explicit dependency on wasm-bindgen version

While having a webpack plugin is nice, I since gave up on wasm-pack & added a build-wasm to my package.json's scripts: https://github.com/serprex/openEtG/commit/9997fb098d168920bb...

This way if someone wants to contribute to openetg they don't need to install my wasm-pack fork

Join us on the official Discord https://discord.gg/qAmfB8T and we can walk you through it. There is a spiritual successor to the game (https://etg.dek.im) and a revival of the game. There are also several methods to still play the original.

Elements. Strictly speaking, this is a collectable card game (MtG style) rather than a true "deckbuilder" but otherwise it sounds exactly like what you are looking for. Heavy emphasis on creative out-of-match deckbuilding and one-off PvE matches. From what I can tell, I think the original game died with Flash, but it appears that fans created a substitute, which I haven't tried: https://etg.dek.im/