Nodes are not Houdini nor are they trying to be. Applying Houdini mindset or having such expectations is not really good idea. Think of nodes rather in terms of generic programming structures. You will see in later lessons that they are very capable but that comes with some cost in complexity
@@CORE4D For example you suddenly introduced "tuples" without saying why or what they are? I think you need to explain each node by itself then explain it in context by connecting it with other nodes or operations. Hopefully that helps.
@@doseofmotion Tuples can be implicitly understood in this context. We believe that viewers are more than capable to absorb that. Explaining each node as you propose would in fact make things way more complicated and saturate the viewer, which goes against your initial statement. Last thing we want to do is go node by node and effectively recite the documentation : )
is it just me or this looks way more complicated than houdini?
Nodes are not Houdini nor are they trying to be. Applying Houdini mindset or having such expectations is not really good idea. Think of nodes rather in terms of generic programming structures. You will see in later lessons that they are very capable but that comes with some cost in complexity
Thanks for the effort but I think you're making things very complicated.
Could you elaborate on what exactly are we making complicated? We are using the system as it is intended to be used with all the associated paradigms.
@@CORE4D For example you suddenly introduced "tuples" without saying why or what they are? I think you need to explain each node by itself then explain it in context by connecting it with other nodes or operations. Hopefully that helps.
@@doseofmotion Tuples can be implicitly understood in this context. We believe that viewers are more than capable to absorb that. Explaining each node as you propose would in fact make things way more complicated and saturate the viewer, which goes against your initial statement. Last thing we want to do is go node by node and effectively recite the documentation : )
@@CORE4D Up to you man, I'm not here to argue. It's too complicated for me at least, don't know about others. Cheers.