61–70 of 198 posts
Earlier quoted context omitted.
Are you referring to the license? Cause the source seems to be open as in "available on GitHub".
That's not what open source means. Open source licences are well defined and listed here https://opensource.org/licenses With extra restrictions, n8n is at most "source available".
(And BTW I like OSI’s definition!)
Instead of claiming the words “open source” always mean OSI’s definition, it’d be better to clarify up front that you’re talking about OSI’s “Open Source Definition”, which is (effectively) a trademark or term of art and does not preempt all possible definitions of the phrase. (Special note that the words “open source” do not always refer to code.)
The turf battle over the words free and open seems silly to me, with both sides arguing that the other side’s word literally means something other than they intend. Stallman has argued that open means source available, and OSI has argued that free means price. Both sides are right, and both sides are stubborn too.
Shame it's not FOSS. There's still https://www.windmill.dev/ though.
Earlier quoted context omitted.
This comment got me digging, n8n actually has a pretty good post-open source license[1] - I'm glad to see more successful examples of this sort of licensing in the wild [1]: https://docs.n8n.io/sustainable-use-license/
It's great and all that their business strategy is working out, but anyone looking to use a FOSS solution isn't going to care at all. This is basically just allowing self-hosting of a third-party's cloud, which is an improvement over traditional SaaS, but shouldn't dilute the FOSS label.
Shame it's not FOSS. There's still https://www.windmill.dev/ though.
This is not an argument in favor of n8n.
Kudos to the n8n team! Seems like the focus is increasingly shifting to AI. Question to folks who’ve used n8n extensively, I’m curious, what are your experiences with n8n, and how much does it end up being a web of verbose “visual python” in practice? I’m very much biased here and have a vested interest, because I’ve been working on a new product not far from this space, but much more oriented at technical users (pla…
n8n in my experience using it for 2 years now, and compared to similar solutions as there are many doing quite the same thing: it is just a very good product. It's stable. It has a gazillion integrations out of the box and is architectured as a module system so it's easy to create your own. It is very community centric, with community workflows and also integration modules people kindly publish on GitHub. Oh, it's op…
I've been evaluating n8n as a way to build things quickly for clients, but I do wonder about what happens when they want to turn the automation into a full app. I wish there was a first-party way to export an n8n workflow as a plain Python script or set of scripts.
Have you ever had to migrate a project from n8n to code?
Earlier quoted context omitted.
It's great and all that their business strategy is working out, but anyone looking to use a FOSS solution isn't going to care at all. This is basically just allowing self-hosting of a third-party's cloud, which is an improvement over traditional SaaS, but shouldn't dilute the FOSS label.
Sir, this is a VC forum for people that are trying to make money
Earlier quoted context omitted.
PM (at the next sprint meeting): "So, Matt, for your next story here's this 48000 line code base that I vibe coded for the new vendor interop feature you said would be difficult to implement correctly. Of course this is a standalone page written in some language that I forget. I think Cursor mentioned some animal name... anyway. Can you please put this into our product please?"
I wish I had gone into medicine like my parents wanted
I have come to realize these drag and drop no code solution are good for low complexity solution. If project scales, it is better to write code. I kid you not, we use another no code solution at work and it was originally meant for PM to create workflows. It came to us the devs to make it and we resent daily working on it. Our life would have been much similar if our workflows had been written in code.
They get a readme, compose.yaml and git repo.
This has worked for set-it-and-forget-it experience.
I tried n8n but for some automation needs, it just wasn't flexible and/or I'd have to build a custom module. My choice was custom code in n8n or custom code in whatever.
147k stars and currently the 38th most starred repo on all of GitHub [0, 1]. Seems odd that a project has so many stars yet is largely unfamiliar to much of HN (corrections appreciated). I asked an LLM if there's ways to detect suspicious starring activity (e.g. if stars were purchased). It suggested checking the project's star history [2] (doesn't appear suspicious). It also suggested the stars to issues ratio. n8n…