Been following the creators for awhile and very much happy to see them democratizing their difficult skillset.<p>Most designers -- think anyone using figma -- are effectively locked out of modern interactive and animated visuals due to not knowing hardcore shaders + effective js coding. To get a feel for how hard that is, look at the public timeline of Shirley Wu, another wonderful award-winning designer and experienced js coder, to pick this kind of stuff up. Nodes makes it a lot more accessible, similar to Max/msp for musicians. Once you look beyond the over-claiming, which is clearly nails-on-chalkboard for most engineers and scientists as you are seeing in the comments -- this is a wonderful and enabling project.<p>Extra impressive is they do not seem to try to 'dumb it down'. They are a consultancy and (seem to) try to use it for their own bespoke advanced installations. I don't know how well this will translate to others, but the success of Max msp and super collider make me optimistic that it can grow to those levels. Cycling 74 supports 20+ employees and empowers many musicians, and as Nodes can be used for commercial art (web+tv ads, music videos, landing pages, ...), I can see them being even bigger.
Looks like a new assembly of old ideas that’s different enough it might do better for some purposes. Very exciting.<p>I was about to start prototyping some tool ideas I had in it, but I can’t find it’s source or license info anywhere. By Googling, I found the GitHub repo [0], but it’s empty of code and looks to be used for issue tracking only.<p>I can’t see something that’s trying to be an ecosystem being very successful without being open (see: every closed-source language/runtime ever).<p>I couldn’t even find any example code. I tried clicking the examples on the home page. I even tried clicking “Playground” and it wasn’t a link. The only CTA I could find was “Download Nodes”!<p>[0] <a href="https://github.com/nodes-io/nodes-io" rel="nofollow">https://github.com/nodes-io/nodes-io</a>
Wow, somehow looks similar to another site that I discovered few weeks ago: <a href="https://cables.gl/" rel="nofollow">https://cables.gl/</a><p>I googled and found this: <a href="https://nodes.io/story/#background" rel="nofollow">https://nodes.io/story/#background</a><p>> When we set off to create a tool of our own, there were already plenty of different node-based or visual scripting/programming tools and environments; VVVV, Houdini, TouchDesigner, Cables.gl, Vizor Patches, Lichen, MaxMSP, UE4 Blueprints and Origami were among the most popular.
Unpopular idea here (from a hobbyist programmer).<p>I would "kill" for a text editor/IDE/REPL shaped as a spreadsheet where each cell is a block of code with 2 possible views (text or result) linkable to other cells. This "spreadsheet" would be programming language agnostic (each cell could use a different language) and I could organize/format my cells (location, colors, size, etc) as I wish.
I somehow fail to understand what this is, but am impressed by it nonetheless. Is this purely for animation designers with coding skills? I thought animation work is done in editors with even less code required usually, but for me as a developer this seems more approachable.<p>I could not look at the advanced examples on my iPad though.
looks cool guys! I'm working on something similar (won't be so vulgar as to self-promote on your post though) - it's exciting to see more people exploring this space. I think there's a lot of potential in visual programming going forwards; I know it's been explored before but it feels like smart phones pre-iPhone: lots of entries but no-one has captured the essence of it into a compelling product yet (outside of specialist but great tools like Houdini and UE Blueprints).<p>Have you shared this with the Future of Coding community (<a href="https://futureofcoding.org/" rel="nofollow">https://futureofcoding.org/</a>)? They're very excited by these kinds of tools.
Hi all, Damien here, one of Nodes creators. We tried to bring our own take in the visual programming space. We're still in beta and figuring out how people are using Nodes. Happy to answer any question you might have, AMA.
For completeness, here <a href="https://github.com/ivanreese/visual-programming-codex" rel="nofollow">https://github.com/ivanreese/visual-programming-codex</a> is a pretty comprehensive list of different takes on visual/flow based programming through the ages…
>What if programming was about ideas, not semicolons?<p>This is like saying "What if writing was about ideas, not periods?" It already is.
I love this. We need to get out of the usual representations of data and get ‘out there’ a little more. Who said art and science couldn’t coalesce? Nothing wrong with a bit of wackiness. Will be following this closely.
Nodes.io is looking great!<p>*For other HN readers: If you're going to leave a message, can you ask yourself, if it's really worth to be so negative? *
Whenever I see things like this I tend to think back to this:<p>> Largely I think that text is already a highly-structured graphical notation, and that when people try to get "away" from it they're often doing so from a position of ignorance of how very long it took to get to where we are in textual notations, and how very many technical innovations are latent in textual notations. Visually unambiguous yet uniform symbol sets, combinatorial-positional word formation, linear spatio-temporal segregation, punctuation and structured page layout .. these are all technologies in writing that we had to laboriously invent, and they have purposes, advantages! Similarly in coding, we had to invent and adapt technologies from verbal and mathematical notations refined over millennia: lines and columns, indentation, block layout, juxtaposition and precedence, scope, evaluation order, comments, grammars, version control, diff and merge algorithms ... the pile of structuring technologies embedded in the textual representation of programs isn't free, and it isn't useless. So I'm just really cautious when people suggest throwing it all out for some hypothetical reinvention. You need those structures: so you've got an immediate problem of "what are you going to use instead", and a longer-term question of "what makes you think you're not going to wind up right back at the same place ten thousand years of refining graphemes-on-a-page wound up"?<p>(Taken from <a href="https://graydon2.dreamwidth.org" rel="nofollow">https://graydon2.dreamwidth.org</a>)
I agree with some of the other posters who are saying that that it is difficult to figure out what this does or who it is for.<p>There's a huge headline saying "nodes for everyone". So, it's for my grandmother and my son and my uncle too?<p>Looking at the examples I see that there's a lot of cool looking geometry and special effects. So maybe "nodes is for everyone who wants to make cool visual things?"<p>Is it for artists who don't want to have do deal with code? Is it for coders who want their code to be more modular?<p>The best way I can understand this is maybe it's a competitor to something like Houdini, for people who are working at the intersection of art and code, it's like a procedural generation tool for art.<p>I thought it might be something which lets you build cool stuff without much code, but I was disappointed in the lack of modularity of some of the examples -- e.g. the "basic webGL" example in the playground. In that example almost everything interesting is going on in the one shader node.<p>Similarly with the boids example, the entire boid simulation is in one node with Javascript. It's not a reusable node.<p>I think the examples would be a lot more compelling if the nodes were each some trivial piece of functionality than anyone could look at and understand within 30 seconds, but they were put together into impressive creations. Like MIT Scratch for adults.<p>The problem with these examples is that there's too much complexity baked into a single node, which makes it difficult to understand those as reusable nodes. If I'm understanding it correctly, reusing nodes is the whole idea here.
It's hard to overestimate the impact of this technique, though it is 5-10 years too soon. :)<p>What this does is lets people reason about change in massively multivariate data sets. Like GPT level multi-variate. I look forward to seeing this applied to the state of ML models, as this is what we're going to need to express the complexity of a lot of techs we will all depend on.<p>There is a casting pearls before swine problem they will need to overcome, as the level of management understanding to interpret and respond to the changes this framework expresses is going to take some years to get people with that level of technical sophistication into decision making positions.<p>Near term, my impression is it will be amazing for getting funding for scientists of all kinds, and being used in hyper-competitive data fields like americas cup sailing, F1 racing, and spooky intelligence/social media company social engineering analysis, and I could see it being used in a new hybrid of quant trading funds, as any sufficiently advanced data vis is essentially arbitrage. All very rarefied niches with a high degree of autonomy. It may be too cool for making policy or lower level decisions in the near term, but this is super epic.<p>When you look at the recent history of how data viz has impacted fields, it has always been way out ahead of the industries it served. I hacked around with 3D "coral" graph viz back around 99-01 (early CAIDA stuff) for internet security analysis in govt, and in spite of its incredible analytic power, the anecdata was it didn't get traction because it was unmanageably powerful. However, I think we're just entering a data viz renaissance, and this is the bar. Amazing.
Looks like a web based TouchDesigner :) (all originating from <a href="https://en.wikipedia.org/wiki/Quartz_Composer" rel="nofollow">https://en.wikipedia.org/wiki/Quartz_Composer</a> )<p>How does it compare? What's new?<p>Certainly could say somewhere that it's one of these node-based visual programming languages made for artists. Well the node part is in the name at least :).
Tangentially related, I've been thinking about how it is somewhat difficult to describe state machines in regular textual code, and it would be nice to have a drag-and-drop visual interface for mapping out the states and transitions, then tie regular code to the transition events.<p>Is there anything like that out there? Or a good open source diagramming library that might lend itself to prototyping this?
After taking a quick look at existing visual scripting tools[0], it seems like the main feature differentiating this from the others is that the nodes are code modules instead of primitives. I think this is where visual programming can really shine, write modules in a text editor and then wire them up in a visual editor. This gives you the high level, conceptual view of the program flow without the excessively verbose visual spaghetti of wiring up individual operations and control flow statements. I think UE4's blueprints can work this way as well, writing a new node in C++ and then wiring it up, but they're not really portable to the wider development ecosystem.<p>[0] <a href="https://github.com/ivanreese/visual-programming-codex/blob/master/implementations.md" rel="nofollow">https://github.com/ivanreese/visual-programming-codex/blob/m...</a>
This looks like Node-Red, but with less pre-made nodes, and designed to show stuff, I love the idea. Also, maybe this is a problem with my installation, but I only see one type of block "custom". If I'm supposed to use npm to install any blocks that support anything, this isn't an ideal starting point, too little information on getting started.<p>Looking at the examples, I'm a bit overwhelmed with how much new boilerplate code I need to remember in order to use all the fancy GUI. I like the idea of having the code be front-and-center, but if you require me to remember how to use the UI elements, why not make some of that code auto-generated based on some UI widget? I like what you have, but it's so minimalist (or brutalist as someone else pointed out) that I find the actual utility of the visual controls... disappointing.
It took 15 years from the first versions of Context Free Art to get to this point of evolution in that kind of experimental proposals. It's interesting anyway, a cool/creative hobby (I think no more than that)
This seems interesting. It would be really cool to rapidly prototype and modify/refactor apps using this.<p>But it seems to me like the <i>much harder</i> part of this problem is 1) developing the nodes, and 2) ensuring that the nodes have the appropriate (sufficiently flexible/extensible) API for connections.<p>I guess what I'm saying is that this needs a "standard library" of nodes - at multiple layers of abstraction - if it is to gain traction. This is especially true, given that there are several other projects that are at least functionally equivalent.
I need something like this to let non-programmers create some basic JavaScript scripts/flows in an app I have. Obviously would need to be some level of power user but hopefully doesnt require them to know how to code. Has anyone tried this or any of the related projects and have an opinion or experience on what works best for a “normal” user?
Looks quite interesting, I always had a found spot for visual languages.<p>The problem with visual spaghetti is the same as with monoliths, lack of understanding how to modularize the code.<p>I think applying digital circuit design best practices to such tools would help more people to properly modularize their boxes.
Seems cool and very interesting. I don’t have too much to add beyond giving praise due to the sheer number of low-quality replies on this submission.
If the people who made this are reading; don’t let an off-day on hn discourage you.
There is a similar project for building web services visually: <a href="http://blyss.tech/" rel="nofollow">http://blyss.tech/</a>
Ohhh, this looks like Cycling 74's Max MSP.<p>Lot of seeming derision in the comments but I LOVE Max and this is an amazing step in that direction for visuals.