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...
Well, I think a lot of the uptick happened last week because that's when it was published in the Toughtworks Tech Radar for this quarter. The audience is large, presumably larger than HN, and that's how I found out about it and have been toying with it since then. I have no idea what I'm doing, but as far as I can tell, this seems like a legitimate project.
Dify, a visual workflow to build/test LLM applications
121–129 of 129 posts
Re: Dify, a visual workflow to build/test LLM applications
#122> 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 adjus…
genuine question - out of the closed-source/commercial licenses, which ones are the most developer friendly ?
But usually you could just go with something like SSPL - which has sufficient protections for the developer (but not the user).
Re: Dify, a visual workflow to build/test LLM applications
#123> 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 adjus…
You've put it way too politely IMHO. It's a license designed to attract contributors to help build their product for free, but leaves space for them to just re-license the product and sell it when the opportunity arises. It's not like we haven't seen this play already, and it hurts both contributors and users...
Re: Dify, a visual workflow to build/test LLM applications
#124Re: Dify, a visual workflow to build/test LLM applications
#125Re: Dify, a visual workflow to build/test LLM applications
#126Where are all these workflow apps getting their ui from? Is there some JavaScript library for boxes connected with lines?
Re: Dify, a visual workflow to build/test LLM applications
#127Wow 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...
> Github stars for this project could also perhaps be artificially inflated? Maybe, but I don't think so. The number of people engaging with the project is what I would expect from the number of stars received. https://devboard.gitsense.com/langgenius?r=langgenius%2Fdify... I've seen projects with 5,000+ stars in a month and only have 20-30 people interacting with the project. Full disclosure: This is my tool
fyi typo
Re: Dify, a visual workflow to build/test LLM applications
#128How does this compare to n8n? https://github.com/n8n-io/n8n
Re: Dify, a visual workflow to build/test LLM applications
#129Where are all these workflow apps getting their ui from? Is there some JavaScript library for boxes connected with lines?
Yes! https://reactflow.dev/ is what I’ve been using, has been great.