Yes… and also no.
Missing features and the learning process are highly connected I think. The features and software capability form part of the approach, method, and therefore must form part of the learning process.
I think there are many things that are and should be different in Rhino, and I appreciate that.
What is blocking you from learning the “rhino way” vs the “other” way?
This to me is the premier problem. If you are wanting to attract people to the right software to the job, you don’t want ex-students running a million miles in the other direction because it takes them an 10 minutes to do what Plasticity does in… a click? A pull?
Actually, in that video Steve posted, that video gave such contrast where a few operations I think Rhino would either do it faster and even do it better.
But I think with that comes the really, really massive issue that these programs are doing slick things that is the right method, and the right way to learn. Despite the advantages of Rhino, this then makes the other guy’s software the right software, objectively.
So to I hope give a clear answer, what often blocks me from learning the Rhino Way is the fact that instinctively and objectively, I know that it is the old or even wrong way in 2024. It feels like the wrong way. Especially if you know you may have an employer who doesn’t want you to take 25 minutes to make a G2 Y blend.
10 seconds in, this remarkable surface change… can I learn to do this in Rhino?
Another interesting example
Features starting at 4 mins in…
Wait a minute, if you happen to have seen @sgreenawalt video… you can find a bit of the functionality. This is fundamental stuff to learn and be integrated.
Oh no! It’s still in a YouTrack!
https://mcneel.myjetbrains.com/youtrack/issue/RH-54659
I think the point here is that anyone, not just students, should learn with the right tools if they are going into a competitive world. The videos are really great, but the tools are dated, and often for students, dated really matters.
I absolutely beleive that the questions are correct. But not for this version of Rhino. With some of these tools, it’s almost like if McNeel spent time on the topics:
- Fundamental surface manipulation at the CV level (Cyberstrak has already 80% done this, in one function)
- Surface matching and blending
- Functionality of Filleting functions
that would solve sooooo many problems, and make Rhino easier and less painful to learn; and we could skip directly to Rhino 10.