"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
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.
"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
"You agree to think carefully and always reflect about what you do and why you do it" or something to that effect. I thought I was so clever at the time.
If you want to be funny, put an easter egg in your code, don't mess with your license.
I don't write code for corporates, so my license is purely fictive. I cannot enforce my license but I can prevent corporates from taking my code and wrapping it into a product and selling it on for a profit. While not passing on a cent to me.
If a corporate wishes to use my code, then they are welcome to pay me a license fee or a one-off payment for a non-distributable license.