Hi There! I just found this and was amazed: https://noisecraft.app for example: bounding balls - NoiseCraft (press play top right) Basically node-based visual-coding for synths! Its all open source and available at github. Warning: very addictive for people who like viewing flows and now listening to them :slight_smile:

[image] gregorius: [image] Colin: Are you assuming that a node that does not have any updates for a period is unmaintained? Sorry I might have mis-intrepreted your question: this isn't about whether packages are maintained or not, this is about maintainers being active or not. So if a maintainer does not update their package than yes it could be there is nothing to update since all works or they have moved on. I assume that they have moved on but that assumption is a conservative, i.e., lower limit. I could make some assumption that X% maintainers are still active even though they no longer create new packages nor update their old packages. But I have no idea how to find out how high/low X is, so I assume it's zero.

[image] Colin: at least replied to by the author Yes, that is a good one. You get lots of issues where you answer but you get zero response back. Then you forget about it, and the issue remains open...

[image] gregorius: Because a company wanting to use Node-RED would like to know how active the community around Node-RED is If I was a company, I would be more interested in how active the contributors are of the subset of nodes that I would use. E.g. when I offer video surveillance survices to my customers, then I am not interested e.g. if the modbud nodes are maintained or not...

[image] BartButenaers: If I was a company, I would be more interested in how active the contributors are of the subset of nodes And if Node-RED itself is no longer maintained? That wouldn't really help then. That's why you also want to know whether there is a healthy community of developers around the core of Node-RED. And most probably the company would maintain their own nodes - if it's for their own hardware. Or fork existing nodes to maintain them in house. A company doesn't like making themselves depended on external developers.

The one that surprises me is the node-red-contrib-flow-manager - not because I've never heard of it (I have) - but because the serial port node, email, random etc are all "extra" ones I include in the script for Pi/debian/ubuntu users - so the fact that dashboard and flow manager are so far and above the others must mean that there is some large scale pulling of those - probably by some containerised deployment - or deployments - or... . Would be interesting to know how it's being used there....

[image] TotallyInformation: I think it would be possible to have a browser-only version - and if my failing memory serves me correctly, I think someone already did that in the past? See this thread - Node-Red in Browser via Stackblitz - #6 by bloigge

[image] gregorius: The main assumption is that if a maintainer isn't updating their packages, they no longer are involved in Node-RED. This is quite obviously a dangerous assumption to make. It most certainly is a dangerous and sometimes unwarranted assumption. [image] gregorius: this isn't about whether packages are maintained or not, this is about maintainers being active or not. I'm concerned where this is going. This is making some very broad assumptions and I'm not convinced they are particularly useful. If I were an enterprise looking to see whether to use Node-RED. I'd be looking for both stability and progression in the core. I'd want more than a couple of developers and I'd want to see involvement over a long period. Then I would compare that against my expected utilisation - is it a temporary tool or a long-term one? As for contributed nodes, I'd only really be interested in there being a vibrant community. Though for specific uses, obviously, I'd also then look into detail about useful contributed nodes. But then I'd be looking to see how good the code was not just whether it is being well maintained - after all, the nature of Node-RED means that it is potentially pretty easy to fork a node. [image] gregorius: That's why you also want to know whether there is a healthy community of developers around the core of Node-RED. And that is certainly the important point. But it is more interesting to see how many node contributors are also core contributors. And that ratio is, I think pretty low for Node-RED. The core is complex and it feels as though relatively few people contribute. However, that is also balanced by having folk from Hitachi and perhaps elsewhere contributing. This is not an easy subject and I think we need to be careful about the messages we are putting out. Not saying you are wrong to do this, just a word or two of caution.

One thing that was interesting was discovering new packages, the babylonjs has become a favourite of mine. But the flow managed also surprised me. It does show that folks are interested in fine grain flow management. I was thinking that it be flowfuse customers who would be utilitising the flow manager.

[image] TotallyInformation: As for contributed nodes, I'd only really be interested in there being a vibrant community. Yes I can maintain my nodes with great enthousiasm, but things can change rapidly (due to illness, familly issues, lack of free time, ...). For software like Node-RED, not only the core needs a community but imho also the nodes that are important for your project... One picture says it all: [image] And it doesn't only happen in Nebraska, but also in Belgium :joy:

Node-RED

Node-RED Forum

Noisecraft - anyone heard of it?

General

dceejay 29 October 2023 17:45 88

See this thread - Node-Red in Browser via Stackblitz - #6 by bloigge

Topic		Replies	Views
[Article] Node-RED Development: The Numbers General	10	609	3 November 2023
Node-RED Survey: Shaping the Future of Node-RED's User Experience News	105	3655	6 October 2025
Best practice: custom v. function node Developing Nodes	38	1924	28 November 2023
Basic drawing tools in NR editor Feature Requests	54	8241	3 April 2020
[Article] Node-RED terminology General	19	1007	31 July 2023

Copyright OpenJS Foundation and Node-RED contributors. All rights reserved. The OpenJS Foundation has registered trademarks and uses trademarks. For a list of trademarks of the OpenJS Foundation, please see our Trademark Policy and Trademark List. Trademarks and logos not indicated on the list of OpenJS Foundation trademarks are trademarks™ or registered® trademarks of their respective holders. Use of them does not imply any affiliation with or endorsement by them.

Noisecraft - anyone heard of it?

Related topics