erlang-red

If anyone with time, money and resources wants to revive the ideas of Yahoo! Pipes then I would suggest using Node-RED[^1] as a good starting point. It has the advantage of being open source, has well defined and stable APIs and a solid backend. Plus 10+ years of constant development with many learnings around how to implement flow based programming visually. I used the Node-RED frontend to create Browser-Red[^2] which is a Node-RED that solely executes in the browser, no server required. It does not support all Node-RED functionality but gives a good feel for using Node-RED and flow based programming. The second project with which I am using Node-RED frontend is Erlang-Red[^3] which is Node-RED with an Erlang backend. Erlang is better suited to flow based programming than NodeJS, hence this attempt to demonstrate that! Node-RED makes sl

Since no one seems to be doing any Erlang, here goes --> I've been working Erlang-Red[1] which is Node-RED flow editor with an Erlang backend. Basically the aim is to implement visual flow based programming for Erlang. [1]: https://github.com/gorenje/erlang-red

Have a look at Erlang-Red[1] which uses Erlang for the basis of making a visual programming environment. Erlang-Red is inspired by Node-RED which itself is inspired by flow based programming. [1] https://github.com/gorenje/erlang-red Disclaimer: I’m the author of Erlang-Red.

> Because data is fully immutable, you get a lot of nice things "for free" This. I discovered this by implementing Flow Based Programming[1] (FBP) in Erlang[2] - the FBP is best suited to languages that are message based and immutable data structures. When using a mutable language, messages are constantly being clone as they are passed around. This does not need to be done using Erlang/BEAM. My feeling is that FBP is a much under-rated programming paradigm and something really worth exploring as an alternative to the current programming paradigms. My take on FBP is that data is being passed to functionality, as opposed to function being passed to data - the functional programming paradigm, or data and function is passed around as is the case with OOP. IMHO it makes sense to pass data to functions, particularly in the times of SaaS and clo

There is Erlang-Red[1] that is bring a visual flow based programming approach to Erlang. That’s something new in the Erlang world. [1] = https://github.com/gorenje/erlang-red

> Different paradigms make different things easier, and thus affect what you are most likely to do with them. 100% this - strangely I just discovered that very thing by taking Node-RED and porting it to Erlang[1]. In doing that, I realised that Erlang has concepts (supervisor, gen_server, gen_statem,...) that would be very applicable to Node-RED and that could be reverse "ported" to the NodeJS based Node-RED. Might do that but the way NodeJS works, it might be more difficult. The reason I thought Erlang would be a good fit for flow based programming are the independence of processes and their communication via messages. This is the exact same thing that happens in flow based programming, so Node-RED should fit well - I thought. > Pure Data's UI works identically on all platforms. How weird - PDs UI is exactly the same as Node-RED only bui

Congratulations for the launch! Also I never heard of that license before: "LICENSE - DON'T DO EVIL" https://github.com/gorenje/erlang-red?tab=License-1-ov-file#... Also I recommend you to put screenshots higher in the readme and also provide real world use case instead of fully abstract examples

Hi There, Erlang-RED has been my project for the last couple of months and I would love to get some feedback from the HN community. The idea is to take advantage of Erlangs message passing and low overhead processes to have true concurrency in Node-RED flows. Plus also to bring low-code visual flow-based programming to Erlang.

Erlang-RED[2] a combination of Node-RED[1] and Erlang to create a visual low code programming environment for Erlang based on the principles of flow based programming. Reached a milestone today by being able to create a http endpoint and route the traffic (based to path variables) between various pathways. Thus it is possible to create a blog using Erlang-RED - what all good frameworks should be able to do ;) [2] = https://github.com/gorenje/erlang-red [1] = https://nodered.org/

I've just gotten back into Erlang becuase of the lightweight processes and message passing, so far behaviour has been secondary (i.e. just learning about them)! The project is about bring visual Flow Based Programming(FBP)[1] to Erlang. FBP seems to be made for Erlang and I was surprised there was something already but there does not seem to be. My goto tool for FBP is Node-RED and hence the basic idea is to bolt a Node-RED frontend on to an Erlang backend and to have every node being a process. Node-REDs frontend is great for modelling message passing between nodes, hence there is a very simply one-to-one mapping to Erlangs processes and messages. I've implemented some basics and started to create some unit tests as flows to slowly build up functionality. I would really like this to be 100% compatiable to Node-RED the NodeJS backend. For