This software has been so easy to use from day one! I couldn't be more thrilled with it. Being an SME, it is offered on an annual basis free of charge. My network of engineers are amazed I am able to accomplish what I have using this software when the companies they come from are paying thousands for licensing. I also would like to note that Autodesk offer an incredible specialization to really round out your skills via Coursera.
In my humble opinion, if you are working on something related to Statistics, RStudio is your go-to tool. But if you are looking for something in Machine Learning, look out for Python. The beauty is that there are packages now by which you can write Python/SQL in R. Cross-platform functionality like such makes RStudio way ahead of its competition. A couple of chinks in RStudio armor are very small and can be considered as nagging just for the sake of argument. Other than completely based on programming language, I couldn't find significant drawbacks to using RStudio. It is one of the best free software available in the market at present.
The first PRO of Fusion 360 that always comes to mind is how versatile it is. Fusion 360 is the first CAD/CAM software that also includes other key features that CAD programs of this size don't have.
Fusion 360 has a generous licensing structure that gives those just starting out a place to start with a professional level CAD program. As a result, this has helped build up a huge community and user base around Fusion 360.
Fusion 360 is updated on a monthly basis. This has proven to be a huge advantage over Solidworks (something else I use) which is only updated once a year. The nice thing about monthly updates, other than regular bug fixes, is that the team can adapt quickly and no one is taken by storm with a big overhaul of the UI or features at the beginning of the year.
The support is incredibly professional and helpful, and they often go out of their way to help me when something doesn't work.
The one-click publishing from RStudio Connect is absolutely amazing, and I really like the way that it deploys your exact package versions, because otherwise, you can get in a terrible mess.
Python doesn't feel quite as native as R at the moment but I have definitely deployed stuff in R and Python that works beautifully which is really nice indeed.
Fusion 360 is a very simple program, so once you begin to draw more complex 3D models, the software gets sluggish and loses its fluidity.
It would be really nice if Fusion 360 could output a model as a SolidWorks file so I can begin to draw something out in Fusion 360 and then pick it up in SolidWorks when I need to do some more advanced functions.
Because Fusion 360 is a simpler program, there are a few functions such as 3D sketches that are not intuitive like all the rest of the functions are.
Python integration is newer and still can be rough, especially with when using virtual environments.
RStudio Connect pricing feels very department focused, not quite an enterprise perspective.
Some of the RStudio packages don't follow conventional development guidelines (API breaking changes with minor version numbers) which can make supporting larger projects over longer timeframes difficult.
There is no viable alternative right now. The toolset is good and the functionality is increasing with every release. It is backed by regular releases and ongoing development by the RStudio team. There is good engagement with RStudio directly when support is required. Also there's a strong and growing community of developers who provide additional support and sample code.
Because the tool is very useful and easy to access, it provides very basic and useful tools to start in the modeling part despite being basic processing aspects. It is also very easy to get a free, temporary, or student license, which makes it a very good CAD tool.
For someone who learns how to use the software and picks up on the "language" of R, it's very easy to use. For beginners, it can be hard and might require a course, as well as the appropriate statistical training to understand what packages to use and when
RStudio is very available and cheap to use. It needs to be updated every once in a while, but the updates tend to be quick and they do not hinder my ability to make progress. I have not experienced any RStudio outages, and I have used the application quite a bit for a variety of statistical analyses
Support is conducted via internet Q&A boards; newcomers to 3D modeling may find that articulating their questions in the language of CAD software is the tricky part — once they find the right technical term for what they're trying to accomplish, answers come quickly. Autodesk also provides a large library of educational tutorial videos that make the initial process of learning Fusion 360's interface much easier.
Since R is trendy among statisticians, you can find lots of help from the data science/ stats communities. If you need help with anything related to RStudio or R, google it or search on StackOverflow, you might easily find the solution that you are looking for.
Autodesk Inventor excels at daily core engineering tasks. When integrated with Vault management systems and part libraries, Autodesk Inventor is tough to beat when you need a mechanical design solution. When Inventor and Vault are setup properly it allows for a very efficient design workflow. I think it would be difficult to achieve the same amount of workflow efficiency with Autodesk Fusion 360, that said, Autodesk Fusion 360 offers a very good toolset at a much lower cost. I can maintain a yearly subscription of Autodesk Fusion 360 and get about 85% of the functionality that is available via the Inventor design suite for the cost of about 2 months of an Inventor subscription. I then also get access to manufacturing plugins with Autodesk Fusion 360 but lose a lot in the drawing environment. Inventor beats Autodesk Fusion 360 hands down when it comes to documentation.
RStudio was provided as the most customizable. It was also strictly the most feature-rich as far as enabling our organization to script, run, and make use of R open-source packages in our data analysis workstreams. It also provided some support for python, which was useful when we had R heavy code with some python threaded in. Overall we picked Rstudio for the features it provided for our data analysis needs and the ability to interface with our existing resources.
RStudio is very scalable as a product. The issue I have is that it doesn't necessarily fit in nicely with the mainly Microsoft environment that everybody else is using. Having RStudio for us means dedicated servers and recruiting staff who know how to manage the environment. This isn't a fault of the product at all, it's just part of the data science landscape that we all have to put up with. Having said that RStudio is absolutely great for running on low spec servers and there are loads of options to handle concurrency, memory use, etc.
Using it for data science in a very big and old company, the most positive impact, from my point of view, has been the ability of spreading data culture across the group. Shortening the path from data to value.
Still it's hard to quantify economic benefits, we are struggling and it's a great point of attention, since splitting out the contribution of the single aspects of a project (and getting the RStudio pie) is complicated.
What is sure is that, in the long run, RStudio is boosting productivity and making the process in which is embedded more efficient (cost reduction).
