Skip to content
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

Typescript pipelines #251

Open
canadaduane opened this issue Dec 3, 2024 · 4 comments
Open

Typescript pipelines #251

canadaduane opened this issue Dec 3, 2024 · 4 comments
Labels
question Further information is requested

Comments

@canadaduane
Copy link

I see pipeline "Code" nodes can have code written in Python. Will it be possible to write "Code" nodes in typescript?

@skull8888888
Copy link
Collaborator

@canadaduane Yes! We're actively working on it. Is there a specific reason to use TS over Python or are you just more comfortable with TS?

@dinmukhamedm dinmukhamedm added the question Further information is requested label Dec 3, 2024
@canadaduane
Copy link
Author

I was exploring/contrasting Lmnr and Dify. Currently our team of ~10 engineers is typescript-focused due to our building a user-friendly nextjs app for students and teachers.

@skull8888888
Copy link
Collaborator

interesting, I didn't know you could write code in Dify. Are you just building a prototype or you are considering using either Dify or Laminar pipeline builder for production use case?

@canadaduane
Copy link
Author

It's a production use case. We are switching everything over from a "code + prompt registry" style of workflow to a combined visual workflow.

A comment I made to another product team that was building a prompt registry and eval framework we had been considering:

The main job-to-be-done is organizing representations of "what is happening" inside the black box so that both engineers and prompt specialists can co-create, understand, critique, and collaborate. I think Dify handles that at a higher level that made sense to both teams--as long as we generate a type-level contract around the boundary between Dify workflows and the rest of our app, the compiler can also help us stay on track.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

3 participants