Thank you, Josh, for your comments. I really appreciate that, and my apologies if I came off a bit negative. But there is a major issue in the AEC portfolio that I would like to address.
There’s a reason why many architects use Rhino, Maya, and other freeform modelers in architecture because the current software that Autodesk develops for architect simply don’t provide the tools we need. Dynamo, which was extremely promising at its conception, unfortunately, has matured more into a solution for handling data and repetitive task rather than a mixed bag of advanced modeling tools that are crucial for geometry creation. This is more so evident at Autodesk University, where pretty much all classes showcase studies of Grasshopper, which is used throughout the whole design process followed by dynamo for data between Revit. As a matter of fact, there was even a well-known AU class two years ago that discouraged the use of dynamo as it’s too slow and less agile as a design and modeling tool and encourages the use of Grasshopper.
Don’t’ get me wrong, as a software company; I do understand that the development direction of an application is partly determined by customer feedback. Users who need more advanced modeling tools simply don’t use Formit or Revit for that matter, which leads to a very on sided development. On the other hand, as a software developer who’s not practicing architecture daily, only references what he sees on his commute to work. And let’s be honest, buildings in the US are generally very conservative, conventional, and generic, which doesn’t require all the bells and whistles of the likes of a program like Fusion. At the same token, it does feel somewhat strange that a phone case designers who knocks out $5 phone cases from his garage get an overkill on modeling tools, yet an architect who designs and develops $50 million building projects gets the short end of the stick