←back to thread

Show HN: Visual flow-based programming for Erlang, inspired by Node-RED

(github.com)

202 points Towaway69 | 1 comments | 16 May 25 14:54 UTC | HN request time: 0.204s | source

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.

Show context

mystraline ◴[16 May 25 16:55 UTC] No.44007580[source]▶

>>44006231 (OP) #

I was an early adopter of NodeRed. Earlier, it worked exceptionally well.

Now? Not so much.

Well, that's not exactly true. Base NodeRed works as well as before. But the libraries of modules to interface with all sorts of websites, APIs, hardware, and other stuff is rotten to the core.

Most plugins/js modules either just don't work, or 'successfully fail'. The easier fail case is where the module can't be installed due to ancient (6mo or older JS, sigh) modules.

I abandoned NR because its basically a hyper-speed bitrot due to terrible library module versioning. And I didn't want to reinvent the wheel on every system I wanted to touch.

replies(4): >>44007710 #>>44007764 #>>44008976 #>>44009882 #

1. wslh ◴[16 May 25 17:07 UTC] No.44007710[source]▶

I don't think this is easily to solve, in general. Similar orchestrators (e.g. n8n) have the same issues because there are a lot of components dependencies that change with time and there is no real cohesion between the core and all kind of plugins. Probably a future "contracts/manifests" linking orchestrators with components could help.