Should we deprecate this module since importing with `npm:mongodb` is working well with Deno?

npm:mongodb pros:

• almost all driver features are working for me
• maintained by mongodb inc
• universal api style for both node and deno

cons:

• ~requried --unstable flag~ it’s not compatible with Deno Deploy for now
• uses node’s Buffer instead of Uint8Array
• uses node’s Stream instead of async iterator and WebStream
• is not fast as x/mongo because uses node compat layer

[jtoppine]

Well, since this issue is in question format, might as well give my 2 cents.

It would be sad to see “native” deno mongo driver go, or fall into disrepair. Deno driver has the potential to be cleaner, prettier and faster, and the npm compatibility layer is big, complex and slow-ish to load.

It seems to also be true that there is a lack of maintainers to keep working on the Deno driver. And that it needs nontrivial amount of work to be good enough for widespread production use. Since the userbase is small for now, and the node driver is usable already as-is, it may be unrewarding to work on the Deno driver.

Maybe the best solution for now would be to put a big banner on the readme, with:

• “call for maintainers”
• a note about the deno driver being alpha/beta quality, maybe detailing some of the most important missing features (automatic reconnect etc)
• a note to suggest regular users may want to use the NPM driver (for now)

This way regular users would not be discouraged from using Deno because of frustrating problems with unstable drivers. And there would be hope for the project to gain maintainers in the future, or even some “official” support from Mongo, eventually improving the driver beyond the NPM driver 😃

[lucsoft]

We can publish a new module on npm like mongodb-webified. It can benfites both worlds

i prefer that it stays here. Else people could be thinking that it’s not really made for Deno.