Replies: 2 comments 3 replies
-
|
Thanks for the feedback! I fully agree with some of the challenges you mentioned such as difficulty of hiring proficient R users compared with python users. I think that has a lot to do with the snowball dynamic I mentioned. It becomes a chicken and egg situation. Re the liscensing issue: could you please elaborate on that? I know there are a lot of companies using R commercially so I wonder what are the specific use cases/products where the liscense becomes an issue. Also your mention of Rust is interesting. I heard about Julia for DS (though it's promise doesn't appeal to me as I rarely encounter computation time bottlenecks outside big data) but never of Rust in the context of DS. |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Please don't get me wrong. I love R and at my company we both use R and Python but R users in our corporate environment are slowly moving to Python. Why? The reason is simple. Licensing. The following article summarizes it:
https://www.r-bloggers.com/2019/01/how-gpl-makes-me-leave-r-for-python/
A couple of other reasons are: Python community is much larger than R and hence can respond more quickly to users issue. A lot of the most used R package have unadressed opened issue...very often ignored. It also exists on the Python side but it is easier to find someone to help you because of the community. Also when you need to hire someone, finding someone who is good at python is much easier than finding someone good at R.
Finally if you are looking for a job, you can't go wrong with Python. R is a niche programming language. I also see that Java, C++,C# are very much in demand. Finally watch out for Julia and Rust. These 2, although still very new, are coming with very strong arguments and liberal licenses.
Beta Was this translation helpful? Give feedback.
All reactions