typesense / typesense/typesense-website

Comparison to alternatives is misleading

Open
#185 1 comment 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Vue
Stars
66
Forks
201
Avg merge
12d 17h
Merged PRs (30d)
4

Description

https://github.com/typesense/typesense-website/blob/bdbcc64a8b543bd29f36cffc8efc2c2708a8f4b8/docs-site/content/overview/comparison-with-alternatives.md?plain=1#L40

While this was true for Algolia but not anymore, it never was the case with Meilisearch.

https://github.com/typesense/typesense-website/blob/bdbcc64a8b543bd29f36cffc8efc2c2708a8f4b8/docs-site/content/overview/comparison-with-alternatives.md?plain=1#L42-L43

In assessing the readiness of a product, one could argue that it hinges on having users in production who experience satisfactory service quality. By that measure, we currently boast a user base of over 20,000 individuals utilizing the open-source edition, coupled with over 1,000 users on our cloud platform. Most of these users actively employ the software in live environments, often handling substantial datasets. Furthermore, we would appreciate you clarifying your definition of "large datasets." Notably, we have clients leveraging Meilisearch for datasets exceeding 100 million documents. This is a considerable scale for most users. We would appreciate your perspective on this matter.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Open docs-site/content/overview/comparison-with-alternatives.md and review the statements around lines 40 and 42-43. Check the claims about Algolia, Meilisearch, product readiness, user counts, and dataset size against the issue, then update the comparison so it is not misleading. Done means those cited statements accurately reflect the reported context.

Written by the indexing model from the issue text.

Assessment

Domain
documentation
Issue type
Documentation
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.