Live data from Hacker News

Rete – JavaScript framework for node-based visual programming

github.com

1–10 of 25 posts

Re: Rete – JavaScript framework for node-based visual programming

#2
Really nice, haven't figured out what it's capable of, but reminds of a similar interface I wrote from scratch about 15 year ago in Java Swing. Blows me away how powerful browsers and JS have become. Really amazing that you can do this with so few lines of code, compared the (tens of?) thousands lines I wrote to do similar.

Re: Rete – JavaScript framework for node-based visual programming

#4
post #3

Any time I see something like this I'm reminded of Yahoo Pipes and how ahead of its time it was. Is there anything like it that's designed for enterprise ETL these? It occurs to me it's a much better way of thinking about data flow problems than code.

I think https://flow.microsoft.com/en-us/ intends to be an enterprise version of this idea, but I've never used it.

Re: Rete – JavaScript framework for node-based visual programming

#7
post #3

Any time I see something like this I'm reminded of Yahoo Pipes and how ahead of its time it was. Is there anything like it that's designed for enterprise ETL these? It occurs to me it's a much better way of thinking about data flow problems than code.

I think https://flow.microsoft.com/en-us/ intends to be an enterprise version of this idea, but I've never used it.

for enterprise ETL - there is also kettle which has been around for a long time- which has a desktop and web authoring client. https://github.com/pentaho/pentaho-kettle

Re: Rete – JavaScript framework for node-based visual programming

#8
post #3

Any time I see something like this I'm reminded of Yahoo Pipes and how ahead of its time it was. Is there anything like it that's designed for enterprise ETL these? It occurs to me it's a much better way of thinking about data flow problems than code.

Node based / dataflow UI are also the bread and butter of CGI and compositing industry. It's hyper efficient both for machine because it's often freely memoized/cached and user (think of it as a simplified haskell at your fingertips) because the stateless and unlimited-undo aspects.

I'm still pretty sure it should be the default UI for half computer introduction. Text for the rest, with the right paradigm of course.

Post reply on HN