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.
For writing out longer code creation for shaping data on complicated reports, the clean UI is helpful. If exploring data though, SAS Studio would be better suited given its easier interface for GUI graph building.
Ability to scale across the company is limited based on the users license, cannot share a dashboard to the general view of the company.
Ability to retain session - not simple method to customize view per user (e.g., once session is ended, the users will return next time to the baseline view).
Ability to enable communication between multiple users - leave notes, tag other users, or share specific view.
I would like to see advance interactions with external databases to be able to kill ongoing queries from SAS. As of now, you can stop pretty much any ongoing process besides the one running on a remote database (killing SAS/EG doesn't stop the remote process)
When creating prompts for programs, it would be nice to be able to have conditional prompts (based on the selection of other prompts). The prompts are clearly a recent feature and constantly under development but I wish it would be more powerful.
More of a SAS metadata issue but when loading SAS/EG (first connection to the server), it takes a few seconds which feels like a long time. I really don't understand why the initialization of the session can take so long. Don't get me wrong, this has no real impact on productivity but that 10s delay just feels really like eternity when you want to run some code in a new session.
There is no other platform that meets our needs. Even if it was terrible we would still use it but fortunately for us it is a very solid project with a great support team. I hope in the future to expand our use and get more licences as well as upgrade to RStudio workbench but for now we are very happy.
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
It's not all bad, but I don't believe that an enterprise purchase of SAS is worth the expense considering the widely available set of tools in the data analytics space at the moment. In my company, it's a good tool because others use it. Otherwise, I wouldn't purchase a new set of it because it doesn't have some of the better analytical functions in it.
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
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.
Although I use SAS support for information on functions, these are SAS related and haven't really come across anything that is specifically for SAS EG.
I've not worked hands-on with the implementation team, but there were no escalations barring a few hiccups in the deployment due to change in requirement & adoption to our company's remote servers.
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.
Python-based platforms like Pandas or Spark are very good too at displaying data and do exploratory analysis. I definitely prefer them to SAS EG. It's just too slow, and doesn't let you peek into the data very easily. Lots of clicking, and I'd rather just write some code, rather do clicking.
I think that RStudio scales pretty well based on the size of the datasets I'm using. It has multithreading capabilities unlike some other statistical analysis programs which is very useful in cutting down on time. The format of RStudio's syntax also makes it very easy to replicate regardless off the scale of the analysis and data set
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).
