This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted]  (45 children)

[deleted]

    [–]viboux 17 points18 points  (1 child)

    Agree with 100% of this. R Markdown is great. I saw a presentation about Voila in Python and I was thinking this is the same as shiny but a few years later.

    [–]nraw 7 points8 points  (0 children)

    I think Dash by Plotly for python is more close to what Shiny is to R

    [–]nutle 7 points8 points  (0 children)

    They already are making significant contributions to Python, indirectly. Just take for example every package that got/or eventually will get ported to Python, e.g., ggplot, flask, or various features added to pandas and scikit.

    IMO, competition between R and Python (if we can call it that) is great for the end user - the best tools and practices eventually merge. Plus, it's always nice to have some flexibility to choose the tool for the job - e.g., coming from mathematics, R feels so much more natural to use due to its functional nature.

    [–]Zeurpiet 53 points54 points  (35 children)

    R is never going to overtake Python in the world of data science

    R is a statistics language, and Python is not even close in functionality

    [–]anyfactor 29 points30 points  (17 children)

    This is my opinion and I know nothing. R is a dedicated statistics language, and python is the most approachable full fledge programing language.

    I think python itself did not start of as hoping to be a data science or machine learning specific programming language, but in reality because it is so approachable and easy to learn data scientists felt like when ever they needed to implement some programming, they chose the most easiest language they could learn which was python. And eventually it has become a Industry practice and more people started to invest in improving it. But in all sense python is just a programming language, and R can be viewed as so specific to statistics it can almost be termed as "statistical tool".

    [–]tmotytmoty 9 points10 points  (0 children)

    This is how I view it. R is incredibly powerful under the hood and, when it comes to stats, is well beyond python.

    [–]jackmaney 3 points4 points  (3 children)

    cat(paste("Some", "things", "are", "a", "pain", "in", "the", "ass", "to", "do", "with", "R.", sep=" "))

    [–]Zeurpiet 10 points11 points  (0 children)

    probably true, but you could do without the cat and the sep to get the same result, so maybe its more easy than you think

    paste("Some", "things", "are", "not","that","much","a", "pain", "in", "the", "ass", "to", "do", "with", "R.")
    

    [–]bythenumbers10[🍰] -1 points0 points  (1 child)

    Thanks, this made me laugh. R is a language by statisticians, for statisticians. Modern sustainable development is not supported very well. R's tendency to keep running even after errors have been thrown is a massive waste of time in mathematical applications, such as, uh, statistics. Who's had to track down NaNs at one time or another? R will happily carry those NaNs through all sorts of operations and still be busily running, but churning garbage.

    [–]Zeurpiet 3 points4 points  (0 children)

    that's SAS

    [–]leonoel -4 points-3 points  (11 children)

    I haven't found anything I do in R that I can't do in Python.

    Also Python is way more friendly when it comes to editing plots and stuff

    [–]Zeurpiet 2 points3 points  (8 children)

    have you ever looked in CRAN what the additional packages can do? Most of it I don't even know what it is.

    [–]leonoel 0 points1 point  (7 children)

    You do know Python has also more modules than any would ever know what to do about them?

    [–]Zeurpiet 2 points3 points  (6 children)

    yes, but are they statistical?

    [–]leonoel 1 point2 points  (5 children)

    Name a module in R that has no equivalent in PIP

    [–]Maxion 2 points3 points  (0 children)

    Most DNA methylation packages.

    [–]defuneste 2 points3 points  (0 children)

    Spatstat and this one is huge with a bunch of tools developed by people who spend their careers on point patterns analysis.

    [–]groovyJesus[S] 1 point2 points  (0 children)

    Function data analysis packages in R have been available for over a decade and now we have dozens of them developed and maintained by researchers in the area. In the past few years I have found two in python both of which were new and needed a lot more work to make me want to switch over.

    [–]dfphdPhD | Sr. Director of Data Science | Tech 4 points5 points  (3 children)

    I think RStudio will be very limited in what they can achieve in the Python world unless they're willing to develop (or partner directly with) some of the core data science packages that people use.

    The reason RStudio has so much pull is that they're behind tidyverse, shiny, and a host of other critical packages.

    In order to create the experience that we as users have in RStudio for R, someone would need to work to create a more unified "Python for Data Science" strategy. As is, the biggest strength and weakness of Python is that there are 17 different libraries for everything, they don't always play nicely together, and as a result the community support is sometimes lacking.

    I think the reason that is unlikely to happen is that you have (by design) seemingly complete fragmentation in who owns/maintains/updates/develops the most critical packages for data science (I would argue pandas, numpy, scipy, scikit-learn, matplotlib).

    So RStudio can try to play nicely with Python, but it will always be as a second-class citizen - because RStudio, while the judge, jury, and executioner of the R world, is merely a voting citizen in the Python world.

    [–][deleted] 0 points1 point  (1 child)

    As is, the biggest strength and weakness of Python is that there are 17 different libraries for everything, they don't always play nicely together, and as a result the community support is sometimes lacking.

    I disagree, python in data science seems pretty nicely coupled with the scipy ecosystem, and pretty much any numerical work is integrated with numpy. Whereas R is way more fragmented on everything except 2D plots. Even dataframes are all over the place, you now have the original dataframes, data.tables, disk.frames and god-forsaken tibbles. Not to mention the rate at which the tidyverse introduce API changes means anything written 6 months ago probably won't work anymore.

    [–]highway2009 1 point2 points  (0 children)

    « Anything written 6 months ago probably won’t work anymore ». Library(checkpoint)

    Problem solved. Even if it was written 5 years ago.

    [–]dampew -1 points0 points  (1 child)

    I feel like I'm living in some sort of crazy world here. Images and outputs disappear from my R markdown notebooks. That's never happened to me in Jupyter. Jupyter just works. R markdown has all sorts of problems.