3 ms·
Namespace conflict, and yes it does matter. Just as "mamba" was an anaconda package manager re-implementation before it got commandeered by the LLM research cro
by Der_Einzige 2y ago
Namespace conflict, and yes it does matter. Just as "mamba" was an anaconda package manager re-implementation before it got commandeered by the LLM research crowd, now Haystack is being stolen away from Deepset: https://github.com/deepset-ai/haystack https://github.com/deepset-ai/haystack
https://haystack.deepset.ai/ https://haystack.deepset.ai/
- trevoragilbert 2y agoAnd this is on top of it being stolen away from the rightful owners: hay farmers.
- 082349872349872 2y agoThey don't make stacks anymore; these days we have balers (and rollers) and therefore move the food (over km) to the livestock rather than the livestock (over m) to the food.
- soulofmischief 2y agoThis is why we have trademark systems. Name conflicts are allowed for commercial use if the purpose and presentation are clearly delineated from competitors. For non-commercial use... who cares? No one is "stealing" words.
- odiroot 2y agoAlso this older Python package: https://django-haystack.readthedocs.io/en/master/ https://django-haystack.readthedocs.io/en/master/
- karmajunkie 2y agoi remember playing with this group’s work back in the early ‘00’s https://haystack.csail.mit.edu/ https://haystack.csail.mit.edu/
- akshaysg 2y agoOur intent is not to steal anyone's name, but I hope that by being a very different product nobody confuses us with this Haystack (or the older Haystack that other commenters pointed out). I do think the idea of a "needle in a haystack" is fairly ubiquitous and makes sense for a ton of contexts to be fair.
- jacknews 2y agoWhich in turn conflicts with https://en.wikipedia.org/wiki/Haystack_(MIT_project) https://en.wikipedia.org/wiki/Haystack_(MIT_project) and numerous others, but so what, as long as they don't conflict in function at the same time.