Posit is far better than Jupyter Notebook and Minitab in this regard that Posit is actually capable of doing all kind of analytical stuffs like data pre-processing, wrangling, validation and visualization. On the other hand, Jupyter Notebook can be used for python programming …
We have considered other editors for R, but no other editor is as feature rich as RStudio. Since RStudio makes an open-source version of their products available, we were able to increase adoption within the organization with zero risk and zero cost and buy into the commercial …
Posit is way way way more reliable than Excel for anything more involved than a quick spreadsheet. Faster speeds, greater charting abilities, flexible functionality and more efficient memory usage. Python is still my go-to for anything that needs integration, but Posit beats …
I've used ArcGIS and ESRI for similar analysis and while both have their advantages, RStudio is much better suited for running advanced statistics and processing large volumes of data. It can also produce quality maps, however, for visually attractive maps and graphs, ArcGIS is …
RStudio is better than python for visualizations but it is less common to use it in many organizations. Excel and PowerBI are better for visualization but, they can only be used for simple models. I would choose R Studio for statistical analysis, ML, or DL because the language …
RStudio works really well compared to competitors such as Jupyter Notebook where there is no environment to visualize variables. RStudio on the other hand is much easier to use and provides the right set of environments for users.
inter-departmental collaboration - my first choice would be TIBCO Spotfire natural language processing and knowledge graphs - my first choice would be Python information security & visualizations (including d3.js libraries) - my first choice is RStudio
RStudio is more than a home for a dashboard. It is a content management system for data science. It hosts models, APIs, runs scripts, AND hosts dashboards.
Verified User
Analyst
Chose Posit
RStudio stacks up pretty well against its competition. For me, it is really up to personal preference and what you are used to when deciding between the competitions. I like that Python packages have the most external resources, so it's easier to troubleshoot. But RStudio does …
The most similar products to RStudio that I have used include IBM SPSS and Tableau Prep. In my experience, SPSS is more intuitive and has less of a learning curve; I used it extensively in my undergraduate career in Statistics and Cognitive Science research. While RStudio has …
RStudio stacks up pretty well against Anaconda. However, Anaconda might be the first choice for someone who likes Python for their analytics and machine learning needs. In the past, I have found it seamless to connect Jupyter Notebook (in Anaconda suite) to integrate with other …
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 …
There are loads of people in the BI (Business Intelligence) space, of course... but I wouldn't touch any of them because none of them offer anything like the R and Python support that RStudio does. RStudio publishes open-source, they're a public benefit corporation, and they …
I prefer SPSS to RStudio, but RStudio is very cheap in comparison to the cost of SPSS. IBM's SPSS does a better job holding the hands of users, but it does come at a very expensive license cost. RStudio is a little bit more difficult to use but is cheap.
Personally, I would prefer SPSS over RStudio and SAS, but the cost for licenses for SPSS deters me from continuing to go with IBM's statistics software. RStudio has the advantage in that it is low cost and there are a lot of available resources on YouTube available for users …
Using [RStudio] requires greater knowledge of statistics and code than SPSS, which has a more simple "point and click" interface. [RStudio] is similar to SAS in its user interface and [requires] the user to write their own queries. [RStudio]'s main advantage is an open-source …
I tried Stata because it's a standard tool for economists but it doesn't have the flexibility and breadth of R and RStudio. I didn't try other IDEs for R.
RStudio is free and so that is the main reason that I use it. I like that it is open source and so there are lots of support on the internet. I tried SAS JMP and Python in a text editor but RStudio was better than either of those options for cost and code flexibility …
RStudio is as good as any software available in the market and is better off than some as it is free. Since it is open source it is improving day by day. I would prefer RStudio over any other tool any day. I would recommend every data analyst to give RStudio a try.
I understand the Jupyter notebook is supposed to be good like RStudio, and I've been exposed to it a little bit. But my experience using it has been very little.
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 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.
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.
I think it's a quick and easy to use tool. The IDE is very intuitive and easy to adapt to. You do not need to learn a lot of things to use this tool. Any programmer and a person with knowledge or R can quick use this tool without issues.
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.
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).