Live data from Hacker News

A personal history of visual programming environments (2021)

nickarner.com

1–10 of 28 posts

Re: A personal history of visual programming environments (2021)

#2
I enjoyed reading this. I knew of quartz composer but I never did anything with it.

I love visual tools and I think they are underutilized today. I cut my teeth in ~2005 with Houdini[0] and Fusion[1] which are both heavily graph / node based (and procedural).

Most recently I have been rekindling my love for visual programming and flow based programming and plan to spend some time in January and February doing more research around flow based programming for infrastructure management.

I plan to get this sort of info published on my website which I have neglected for half a decade or more but if you are interested in visual programming you might enjoy checking these out:

Unit from Samuel Timbó:

https://github.com/samuelmtimbo/unit

https://ioun.it/

A video of me exploring what I figured out about it (while also learning to stream) https://www.youtube.com/watch?v=vwknTfGVDq8

Behave-Graph from Ben Houston:

https://github.com/bhouston/behave-graph

And the products I learned so long ago

[0] Houdini https://www.sidefx.com/products/houdini/

[1] Fusion https://www.blackmagicdesign.com/products/fusion

Re: A personal history of visual programming environments (2021)

#3
post #2

I enjoyed reading this. I knew of quartz composer but I never did anything with it. I love visual tools and I think they are underutilized today. I cut my teeth in ~2005 with Houdini[0] and Fusion[1] which are both heavily graph / node based (and procedural). Most recently I have been rekindling my love for visual programming and flow based programming and plan to spend some time in January and February doing more re…

I played around with Quartz Composer when I had my Macintosh. It was neat finding an obscure app deep in the directory structure that you could use to create interesting visuals. It was like my little secret.

I found out you could use it to create screen savers and iMovie effects. It provided a lot of opportunities to tinker.

The one thing that was annoying was that it didn’t offer a lot of control over the final visuals. I was used to Flash giving you frame by frame control, which you did not have in Quartz Composer.

You could create some cool effects, have some interactivity, but it seemed very limited and niche.

Re: A personal history of visual programming environments (2021)

#4
post #2

I enjoyed reading this. I knew of quartz composer but I never did anything with it. I love visual tools and I think they are underutilized today. I cut my teeth in ~2005 with Houdini[0] and Fusion[1] which are both heavily graph / node based (and procedural). Most recently I have been rekindling my love for visual programming and flow based programming and plan to spend some time in January and February doing more re…

Quartz Composer was IMHO one of the coolest things to come out of Apple ~15 years ago in the early days of their Core Animation layer-based rendering framework. When I was first freelancing, I got a gig working on some displays for a large law firm and chose QC. Was able to do things like fancily display customer testimonials and the like, but have a Mac mini running things which had a shared folder that staff could just drop scans of letters in. It was the best of both worlds — amazing programmatic 3D rendering and Mac ease of use for the non-technical people.

I also used it briefly for some small about box effects in my apps, which allowed me to programmatically insert text or imagery based on the user’s registration or other variable data and just plug it into the inlets in the QC animation that was used.

It was basically a totally programmer-exposed motion graphics package. Too good.

Re: A personal history of visual programming environments (2021)

#5
I remember being blown away the first time I saw the visual programming tool that came with Silicon Graphics workstations.

Visual programming works great as long as you restrict it to a particular domain (e.g. data processing, visualization, audio processing etc).

Re: A personal history of visual programming environments (2021)

#6
I also came at some of this stuff from an early background in electronic music and modular synthesis (which is all about making the connections between functional blocks visual/visceral).

I've used Max/MSP and Grasshopper. I find them really great for building up interactive tools which have a bunch of inputs/controls.

The one down side of these tools is that they can turn into visual spaghetti code which is hard to trace.

I strongly recommend the last two links in the article for their visual catalogs of visual programming environments.

Re: A personal history of visual programming environments (2021)

#7
post #2

I enjoyed reading this. I knew of quartz composer but I never did anything with it. I love visual tools and I think they are underutilized today. I cut my teeth in ~2005 with Houdini[0] and Fusion[1] which are both heavily graph / node based (and procedural). Most recently I have been rekindling my love for visual programming and flow based programming and plan to spend some time in January and February doing more re…

I had a brief encounter with Natron, but could not really understand what is going on in it: https://natrongithub.github.io/#features

Re: A personal history of visual programming environments (2021)

#9
Surprised nobody's mentioned LabView yet! Anybody have experience/opinions using this? Their versioning is one of the worst I've ever seen, but they have a impressively comprehensive ecosystem of industrial test equipment.

https://www.ni.com/en-us/shop/labview.html

Re: A personal history of visual programming environments (2021)

#10
post #6

I also came at some of this stuff from an early background in electronic music and modular synthesis (which is all about making the connections between functional blocks visual/visceral). I've used Max/MSP and Grasshopper. I find them really great for building up interactive tools which have a bunch of inputs/controls. The one down side of these tools is that they can turn into visual spaghetti code which is hard to…

Visual spaghetti gets real bad real quick, but I find the process of despaghettification to be incredibly gratifying. Well routed graphs make my brain produce happy chemicals.
Post reply on HN