BUt the pricing model and deployment story felt odd. The business model around LangGraph reminded us of Next.js/Vercel, with a solid vendor lock-in and every cent squeezed out of the solution. The lack of clarity on that front made us go with Pydantic AI.
Being able to build model/simulations easily and being able to share them with others, who can then even interact with the results, as truly motivated me to try more stuff and build more. I've been deploying more and more of these apps as PoCs to prospects and people really like them as well.
Big thanks to the team!
Help me understand how these two things are on same level, please?
They also say that using LangChain and other frameworks is mostly unnecessary and does more harm than good. They instead argue to use some simple patterns, directly on the API level. Not dis-similar to the old-school Gang of Four software engineering patterns.
Really like this post as a guidance for how to actually build useful tools with LLMs. Keep it simple, stupid.
As I said, they already mention LangGraph in the article, so the Anthropic's conclusions still hold (i.e. KISS).
But this thread is going in the wrong direction when talking about LangChain
https://cohost.org/belarius/post/6677850-architectural-cross
(I am not the author of the blog, nor the original poster, but I just want to share the link because I found this incredibly cool)
It's something about how scientific papers are not "for pleasure", they're informational tools. An easter egg in a game is cool right, but an easter egg in a graphics driver? That's the distinction I'm making here.
Scientific articles are informational tools that report results of experiments and nothing more. If the results are interesting to the peers, they are published. By they are not world's laws made paper unless sufficient replications are made. This means that each article need to be read with the context of the literature in mind and with a critical eye. Each are a single point of evidence to a phenomena.
Hence, there are subjective informational tools, written toward a specific audience (the experts of the domains) to inform of a specific result in a specific case.
On top of that, their are specific journal/issues where these types submissions are allowed. Don't read these submissions if you are looking for serious "information tools"
Scientific literature must be handled the same way as legal literature. If you are not a law expert, you ask a lawyer. If you think you are a legal expert when you are not, surprising consequences may arise.
In universities, they are classes dedicated to handling the scientific literature. They are provided for a reason.
So please, don't use cat's physic for liquid simulation in game engine... or please do?
Any modern tips / life hacks for this situation?
They are a little more focus on scientific computing than uv, which is more general. They might be a better option in your case.