R is overwhelmingly used in bioinformatics. There is nothing quite like bioconductor. Most new tools/methods (for ex, in the scRNA-seq) release R packages first.
Well I'd say conda is quite like bioconductor with the ease of installing relevant packages. scRNAseq has popular r packages like seurat but also popular python packages like scanpy.
Really depends on the application. For clean, concise and reproducible ad hoc statistical analytics and modelling, there isn't a better tool than tidyverse+tidymodels.
It's a classic case of the best tool for the job. I usually create simple stuff in R and then move to bigger datasets and production in py+spark.
Although I agree and don't like R very much, I believe ggplot is still the gold standard for creating top-quality visualizations. None of the python (or other language) clones are quite as good. For projects where the end goal is a complex or detailed graph or plot, it's sometimes worth trudging through R to achieve the best final result.
Yup, not a data scientist but often do data processing to analyze the outcome of experiments (drone-flight related). I'll use Python/Jupyter if there's a significant amount of clean-up that needs to happen, but R/ggplot is unbeatable if I'm trying to look at the data from different perspectives. As an example, I was trying to look at GPS data the other day and ggplot() + geom_point() + geom_density_2d() was an absolutely perfect way to better grok what was going on.
I've used Python since 1995, so I should be biased, but switching from Python to R is a huge productivity boost - like switching from Excel to Python. R is just years ahead.
This is because R borrows a lot of syntax from S. When R came out, statisticians were using S, so it was natural to make it like this. If they went another way, you'd get statisticians in mailing lists 20 years ago bemoaning how its so much not like familiar S, rather than regular old programmers 20 years later today who bemoan that R isn't like familiar python like what happens on HN whenever there is an R thread.
I mean compared to other languages these sorts of quirks might seem like big deals, but they rarely come up. You see that error, you copy paste and find a stack overflow thread explaining it, you know what to do next time and move on. R is certainly no C.
That book isn't so much about R weirdness. It's more about teaching data scientists to consider the implications of practices like copying a huge table in memory on every loop iteration.