Posit, formerly RStudio, is a modular data science platform, combining open source and commercial products.
N/A
Tableau Desktop
Score 8.3 out of 10
N/A
Tableau Desktop is a data visualization product from Tableau. It connects to a variety of data sources for combining disparate data sources without coding. It provides tools for discovering patterns and insights, data calculations, forecasts, and statistical summaries and visual storytelling.
RStudio is code based, so in the beginning tools like Spotfire and Tableau have thier advantages since many things are already built in, but in terms of flexibility RStudio will win over the longer term.
The cost of RStudio and RStudio Connect is very reasonable [for a] small …
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 …
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.
These all work synergistically and fulfill slightly different roles. In general this is determined by complexity of task and the degree of training and expertise of the end user. RStudio works well for organisations looking to move into doing more complex analytics. In general …
RStudio offers less out-of-the-box point and click solutions than other products, but it allows for custom solution development and its integration with the Shiny package in particular allows for the custom development of point and click solutions.
RStudio absolutely offers everything that SPSS does at zero cost. Yes, there is a bit of learning curve in terms of you needing to equip yourself with R language but that's a good thing as you learn and apply more complex statistical tools and techniques on your datasets. …
RStudio works similarly to PyCharm (and PyCharm can support R code) insofar as it's a development environment meant to improve the coding experience and easily provide commonly used resources (packages). They both provide a navigable dev environment with some learning curve. …
We preferred Tableau over Power BI due to its user-friendly interface and interactive GUI. Since we work with large datasets, we observed that Power BI can deal with only a limited amount of data when compared to Tableau which creates complex visualizations in a time-efficient …
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.
Tableau Desktop is one the finest tool available in the market with such a wide range of capabilities in its suite that makes it easy to generate insights. Further, if optimally designed, then its reports are fairly simple to understand, yet capable enough to make changes at the required levels. One can create a variety of visualizations as required by the business or the clients. The data pipelines in the backend are very robust. The tableau desktop also provides options to develop the reports in developer mode, which is one of the finest features to embed and execute even the most complex possible logic. It's easier to operate, simple to navigate, and fluent to understand by the users.
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.
An excellent tool for data visualization, it presents information in an appealing visual format—an exceptional platform for storing and analyzing data in any size organization.
Through interactive parameters, it enables real-time interaction with the user and is easy to learn and get support from the community.
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.
Our use of Tableau Desktop is still fairly low, and will continue over time. The only real concern is around cost of the licenses, and I have mentioned this to Tableau and fully expect the development of more sensible models for our industry. This will remove any impediment to expansion of our use.
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.
Tableau Desktop has proven to be a lifesaver in many situations. Once we've completed the initial setup, it's simple to use. It has all of the features we need to quickly and efficiently synthesize our data. Tableau Desktop has advanced capabilities to improve our company's data structure and enable self-service for our employees.
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
When used as a stand-alone tool, Tableau Desktop has unlimited uptime, which is always nice. When used in conjunction with Tableau Server, this tool has as much uptime as your server admins are willing to give it. All in all, I've never had an issue with Tableau's availability.
Tableau Desktop's performance is solid. You can really dig into a large dataset in the form of a spreadsheet, and it exhibits similarly good performance when accessing a moderately sized Oracle database. I noticed that with Tableau Desktop 9.3, the performance using a spreadsheet started to slow around 75K rows by about 60 columns. This was easily remedied by creating an extract and pushing it to Tableau Server, where performance went to lightning fast
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.
I have never really used support much, to be honest. I think the support is not as user-friendly to search and use it. I did have an encounter with them once and it required a bit of going back and forth for licensing before reaching a resolution. They did solve my issue though
It is admittedly hard to train a group of people with disparate levels of ability coming in, but the software is so easy to use that this is not a huge problem; anyone who can follow simple instructions can catch up pretty quickly.
The training for new users are quite good because it covers topic wise training and the best part was that it also had video tutorials which are very helpful
Again, training is the key and the company provides a lot of example videos that will help users discover use cases that will greatly assist their creation of original visualizations. As with any new software tool, productivity will decline for a period. In the case of Tableau, the decline period is short and the later gains are well worth it.
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.
If we do not have legacy tools which have already been set up, I would switch the visualization method to open source software via PyCharm, Atom, and Visual Studio IDE. These IDEs cannot directly help you to visualize the data but you can use many python packages to do so through these IDEs.
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.
Tableau Desktop's scaleability is really limited to the scale of your back-end data systems. If you want to pull down an extract and work quickly in-memory, in my application it scaled to a few tens of millions of rows using the in-memory engine. But it's really only limited by your back-end data store if you have or are willing to invest in an optimized SQL store or purpose-built query engine like Veritca or Netezza or something similar.
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).
Tableau was acquired years ago, and has provided good value with the content created.
Ongoing maintenance costs for the platform, both to maintain desktop and server licensing has made the continuing value questionable when compared to other offerings in the marketplace.
Users have largely been satisfied with the content, but not with the overall performance. This is due to a combination of factors including the performance of the Tableau engines as well as development deficiencies.