Thanks for clarifying this. I was curious what you were referring to. This meeting was probably about 6 or 7 years before I joined McNeel. I can’t promise I wouldn’t have said anything like this but it does sound like an unrealistic promise to make. But we now have the benefit of hindsight.
We are definitely responsible for the slow development. I would agree that it is a slow process. Cross-platform development is quite challenging, especially in the case of Rhino (the decision to use native UI on both platforms, supporting a plugin architecture, and the list goes on). You likely know all that already, but I think it bears repeating.
Me too. We need to fix that bug. Thanks for reporting it. While researching it, I found a lot of counter-intuitive and odd behavior in Rhino for Windows. Cross-platform is hard.
Features and bugs aside, I believe this will still be a challenge given the decision we made to change many aspects of the user interface in Rhino for Mac; both large and small. This is a major tradeoff and one I hear from educators quite a bit. If the tutor is familiar with one platform, doing a training with students on both platforms poses some problems. I still think we have a lot of work to do on this front.