Include /x/redis as /std/redis

[kt3k]

There seem strong demands/needs of redis client in the community. We should have one in std

ref: https://deno.land/x/redis

ref: https://news.ycombinator.com/item?id=31333025

External dependencies of /x/redis:

• lodash-es/shuffle
• lodash-es/sample
• lodash-es/uniqBy
• cluster-key-slot

[erfanium]

what makes redis different from mysql, postgres, mongodb, elasticsearch,... ? They are all popular. we can't just include redis driver in std and ignore the rest.

and if we add driver support for all popular databases, std would become a real mess. because each drivers has its own CI pipelines, testing structure and dependencies (like mongodb driver that depends on bson).

I don't think std is a place for third party drivers. instead of that, Deno can support denodrivers org so they can continue to develop drivers

[kt3k]

@erfanium We chose to try migrating redis (and sqlite) first because they have comparatively less external dependencies. (Also the maintainer welcomes the transition in case of redis)

We haven't decided on other drivers. We might take different path for other drivers depending on their situations

[piscisaureus]

I'm -1 on this. This is out of scope for std.

There seem strong demands/needs of redis client in the community.

If there is no community provided driver for an important database like redis, we can consider starting the effort. But I still think they should be maintained in separate modules/projects outside of std. The discoverability issue can be fixed with improved search.

[iuioiua]

I'm -1 on this. This is out of scope for std.

I agree. I think we should close this issue.