Projects purposes should be documented, or the project should wind down.

[EvanCarroll]

I see someone asked this earlier,

#50
#44

But it's really confusing for new people when the author says,

On a side note, idb crate with builder feature also provides similar API.

And also, in response to a question for the difference,

Not much (anymore). Initially, idb was a wrapper over web-sys and rexie offered a builder pattern for creating object stores. Later, the builder pattern was merged in idb under builder feature (which rexie now uses).

I find it even more confusing and amazing when you own both the repositories, Rexie and idb. If you have the only value add that rexie offers is the builder pattern, and you've since decided to implement that in idb then Rexie is effectively deprecated right? It offers nothing?

If so, there is nothing wrong with that -- it happens a lot in software but please help the ecosystem clean up.

1. Publish a new copy with Markdown that clearly says the package is deprecated.
2. Put the word DEPRECATED in the title and description.
3. Mark this repository as archived on Github.

This would clear up confusion and point people in the right direction. It's even more confusing when you describe deli as a further abstraction but it doesn't build on rexie, instead it builds upon idb.

---

Also just found #34

[devashishdxt]

Neither rexie nor idb is deprecated. Both libraries are actively usable, and you can choose whichever API you prefer.

They serve the same purpose: helping you interact with IndexedDB from WebAssembly. If you run into any issues or bugs, please feel free to report them, and I’ll look into them.

[EvanCarroll]

The issue isn't for deprecation, it's for clarifying the purpose. The problem apparent is that you've been asked by multiple people and you shrug your shoulders. Which is just wasting everyone's time (theirs for having to ask), and yours for having to provide an answer that doesn't address why the two projects exist.

If the API is different, I would expect something to say how it's different or why you would prefer one over the other. But this was the response,

Initially, idb was a wrapper over web-sys and rexie offered a builder pattern for creating object stores. Later, the builder pattern was merged in idb under builder feature (which rexie now uses).

Which leads me to believe the API is no longer different.

[devashishdxt]

I’ve added a clarification to the README.

Unfortunately, I won’t be able to provide a detailed comparison of how the APIs differ between the two crates in the README. You’ll need to review the APIs and decide which one best fits your use case.