I've been thinking about how I'd like Rhino to evolve for a while. I use Rhino since it was beta in 1997. The first slogan was Nurbs Modeling for Windows.
The first affordable nurbs modeler, everyone remembers this clear target of the program.
Later one huge advantage appears, the ability to be open to plugins, this way you can pay just for what you need and use it for whatever you want, not just modeling.
BUT this strategy seem to be extremely dangerous lately, because many people started being plugin dependent, like me And we all know what happens when a plugins starts to shine too much, like T-Splines.
I also found logical what happened to VSR, the tools they developed are impressive, and for an industry that handles high budgets, their plugin costs more than the Rhino license.
Other thing is that this plugins is almost a Rhino inside a Rhino, many tools are duplicated, with different approach, advantages or disadvantages... What I mean is that when a plugin covers so many important areas of your daily work, this tools should be part of the core of the main program.
From my point of view Rhino without plugins now is a generalist, you can do whatever you want but it's not designed for a specific industry. This gives it strength and weakness. Users ask for features for specific task like solid modeling, surfaces with bezier, subD, jewellery specific commands, Architecture features, history based, rendering, printing...
Although there are many of the requests that are common to all the industries, some others not, and it's understandable the program can't be strong in everything.
Other programs are focused on just modeling, or rendering like Keyshot, and everybody know what it does and how easy is to use it.
My students at the University tend to learn programs with 2 criteria.
1- The standard in the industry.
2- Easy to use.
We may have different versions of Rhino, all with native tools, well integrated. A version could be for Architects, other for jewellers, and other for product designers.
This way you prevent the typical limitations of plugins, no fear of loosing some functionality in the future, and a price for the tools you will use.
I would like some integration of grasshopper in the tools, but without the need of developer skills.
I'm changing this text while I'm thinking :), I just want to contribute with some historical vision and ideas.