Wow I've never seen so many fake accounts on a HN post before. So then is it fair to say the Github stars for this project could also perhaps be artificially inflated? This month they started to go exponential: https://github.com/langgenius/dify?tab=readme-ov-file#star-h...
How does it compare with MagickML?
Very slick and potentially very powerful. After a few minutes playing with it, I have a few recommendations:
- Variables should have more types, like an array of objects
- Prompting should incorporate Jinja2/Nunjucks
- For every prompt, I should be able to create many different test examples, along with an answer key, and measure how well it does across many tests
- It should auto-save. I did a lot of prompting work and then clicked another icon. When I came back, all my work was gone. (In fact, I don't see where to save at all! Maybe I'm just missing it.)
How does this compare to n8n? https://github.com/n8n-io/n8n
What kind of people are using this AI dev platforms?
When do they become better then just rolling your own custom code?
Where are all these workflow apps getting their ui from? Is there some JavaScript library for boxes connected with lines?
Dify looks super powerful! Always nice to see a React Flow app in the wild :)
All these spam comments have pushed this to the top feed
Sorry about all these spam comments lol
> https://github.com/langgenius/dify/blob/main/LICENSE
everyone is apparently a license pioneer
"AI means the end of coding" didn't age well.
It turns out to get the most out of LLMs you need to program them.
[dead]
[dead]
[dead]
[dead]
[dead]
[dead]
[dead]
[dead]
[dead]
[dead]
[dead]
[dead]
[dead]
[dead]
[dead]
[dead]
[dead]
[dead]
[dead]
[dead]
[dead]
wtf is up with all these bots ?
it's ironic they decided to do this on a post about LLMs. Are they feeling threatened that LLMs are taking their jobs ?
[dead]
[dead]
[dead]
[dead]
[dead]
[dead]
[dead]
[dead]
[dead]
[dead]
[dead]
[dead]
[dead]
[dead]
[dead]
[dead]
[flagged]
[flagged]
[flagged]
[flagged]
[flagged]
[flagged]
[flagged]
[flagged]
[flagged]
[flagged]
[flagged]
[flagged]
[flagged]
[flagged]
[flagged]
[flagged]
[flagged]
[flagged]
[flagged]
[flagged]
[flagged]
[flagged]
[flagged]
[flagged]
[flagged]
[flagged]
[flagged]
[flagged]
[flagged]
[flagged]
[flagged]
[flagged]
[flagged]
[flagged]
[flagged]
[flagged]
[flagged]
[flagged]
[flagged]
[flagged]
[flagged]
[flagged]
[flagged]
[flagged]
[flagged]
[flagged]
[flagged]
[flagged]
> Dify is licensed under the Apache License 2.0, with the following additional conditions ...
I am totally fine with closed-source/commercial licenses, but please don't do a "Like Apache 2.0 but not really" type of license. It just confuses everyone.
You can pick from SSPL, BSL, Elastic license among others if you don't want to roll out your own.
> 2. As a contributor, you should agree that: a. The producer can adjust the open-source agreement to be more strict or relaxed as deemed necessary. b. Your contributed code may be used for commercial purposes, including but not limited to its cloud business operations.
This is not very contributor-friendly.
You could consider keeping an open-source core, and extensions for paid features.