←back to thread

199 points Towaway69 | 3 comments | | HN request time: 0.893s | 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
concerndc1tizen ◴[] No.44006463[source]
I've been interested in this for years.

Are there other similar projects that you're familiar with? Perhaps targeting other languages?

What are the major problems with this approach to programming? Are large programs hard to work with?

replies(4): >>44006783 #>>44006883 #>>44006956 #>>44008692 #
Towaway69 ◴[] No.44006783[source]
I know of Py-Red[1] which is an attempt to do the same but with Python. Using Node-RED as a frontend and something else as a backend, no I haven't heard of anything similar.

Main problems with visual flow based programming is the tooling: there aren't any good tools for doing visual comparison nor visual version control. Things like GitHub aren't able to render flow code as seen in the editor.

For Node-RED that means that the Json that defines a flow can be compared but that soon becomes meaningless because semantic changes get mixed with visual changes, i.e., that the x,y coordinates of a node have changed - is meaningless for the logic of the code.

This means that code sharing and collaborative development is difficult purely visually but only because tooling is missing. Compared to textual programming before things like SourceForge or Git and we had the same issues as we do with visual coding now.

Node-RED has a bunch of features to make large programs maintainable. Things like link nodes that allow jumping between flows also allow code reuse. There also subflows which encapsulate repeated code and can be referenced from anywhere.

That's also why I chose Node-RED for this because it seems to be the most mature and best maintained low-code visual flow-based programming tool. There are others such as n8n (which seems to be the other biggie) but they lack the generalness of Node-RED. I can create web sites with Node-RED while and the same time controlling my LEDs via Raspberry installation. Node-RED is extremely flexible.

[1]: https://github.com/mdkrieg/py-red

replies(4): >>44006979 #>>44007188 #>>44007740 #>>44011059 #
1. regularfry ◴[] No.44006979[source]
Speaking of controlling LEDs, there's also https://www.atomvm.net/doc/main/index.html. From a very quick scan it looks like it would need some fiddling (especially around the filesystem) to get it to work, but being able to scale down to smaller devices than a full pi would be very, very interesting.
replies(1): >>44007860 #
2. Towaway69 ◴[] No.44007860[source]
Wow! That does look interesting:

> With AtomVM, you can write your IoT applications in a functional programming language, using a modern actor-based concurrency model, making them vastly easier to write and understand!

> It also supports WiFi networking on devices that support it, such as the Espressif ESP32. All of this on a device that can cost as little as $2!

If ErlangRED made it to a $2 chip, I'd be very happy!

replies(1): >>44009368 #
3. cess11 ◴[] No.44009368[source]
Shouldn't be too hard to get AtomVM onto chips now, according to rumour that's been worked on and made simpler.

This recent talk, https://www.elixirconf.eu/keynotes/the-atomvm-and-new-horizo..., probably showcases the process to some extent so it's a good idea to keep an eye on their YouTube channel for a recording.