-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rename it to LangStream? #4
Comments
I vote to rename. Any association with the word "chain" is incidental, and is not present in multiple of LangChain's competitors, nor many of its own "Lang<*>" derivatives and extensions. "Lite" doesn't really describe the composability benefits of a monadic transform, even if it is technically light-weight at the implementation layer. |
I also vote to rename it |
I vote to call it Languid (having or showing a disinclination for physical exertion or effort) |
according to comments here, on discord and some offline conversations I had, most people think this is a good idea, so thank for voting folks, the rename from LiteChain to LangStream is now done! 🎉 I've released it on v0.1.7 to migrate it should be easy enough, change the dependency and imports from |
Is this the same as https://langstream.ai/ or different? |
I do believe they are very different, this confused me as I found langstream.ai first . |
hey folks, I was considering the suggestion to change LiteChain name to LangStream, and subsequently change the main constructor from Chain to Stream. I think it's a big move to not be taken lightly so I wanted to hear y'alls opinion, but I think it's early enough on the project that a move like this is possible
Some pros for it:
It removes the confusion with blockchain stuff
Stream is a much more well established programming concept, and it's what the library actually do, 'chain' is a neologism in programming, getting popularized in LLMs world because of the chain-of-thought paper and langchain I feel
Make it more clear that you need to consider that everything is streamed when using the library
Some cons:
Breaking change of course
Loses the "lite" part of the name
Maybe make it less clear for people comming from LangChain to make the switch
thoughts?
The text was updated successfully, but these errors were encountered: