That “freeze or crash” only happens because the whole graph is recalculated all the time. In Houdini, if you work on a specific area, you simply set the blue active button to something closer instead of to the end. The rest is just ignored.
And of course you can also kill Houdini with silly stuff, but a bit of intelligence on the user side helps there too.
Oh, and in Houdini, you can always hit Escape to stop computing… Or set it to manual refresh only.
It’s not only the list vs. attributes, the whole thinking and GUI of GH is strongly on the elaborate, clicky, “looking nice but is slow” side.
Like in Houdini, if you select a node, all the parameters are directly visible in a separate parameter window. So you can directly see all the settings and values and change them. In GH it’s all hidden and you need to click that, hover that, click a dozen times there…
And the whole argument above about “it’s the users fault if things are slow” is really hard-core Stockholm Syndrome. If somebody has 64 cores and only one of them is used, that is not the users fault, that is inadequate programming in 2021.
That you can also optimise your own part of things simply is a totally different matter.
And yes, many of the GH nodes are really primitive or don’t give any useful feedback, so that doesn’t help things either.
I’m really thankful to have been on the other side of the fence for a while, gives a rather good perspective how green things can actually be