Hacker News new | past | comments | ask | show | jobs | submit login

I can on reply from the perspective of a multi-year user:

It is primarily functional programming. This means, you have an input, that is processed through blocks (functions) and does some things.

This is GREAT for things similar to IFTTT (If this then that) applications. E.g. you receive a datagramm via MQTT, and then format it, add some info, and upload it into influxdb.

You can also easily add a small dashboard with some buttons and labels for easy home automation.

What needs some working around with context store are side effects, or persistance. I have two examples that can be worked around, but are rather hacky:

1) Reading a list from a homepage, and only sending updates for new items. This is the prime example for context - you save a list of seen items in the context of the function node, so the next invocation can filter out the existing ones

2) Using a switch in the dashboard for selecting between automatic and manual mode. E.g. I want to have my rack fans controlled by the temperature, but with an override to set it manually. This needs a bit more hacking with context where you have two flows into one node, and you have to set the internal state of the context depending on the override button.




Consider applying for YC's Spring batch! Applications are open till Feb 11.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: