RStudio just worked well, looked good, and had everything I needed. I never had a similar urge to use a different IDE with R. VSCode never had those issues, and with the right plugins, it goes from a text editor to a full-blown IDE and looks great doing it. The little details with VSCode worked better than Spyder, which was fun but could be jagged in some respects (variable viewer was incredibly slow even on small dataframes, graphics rendered in separate windows, UI could be buggy, slower startup, occasional crashes, etc). py files (rather than Jupyter Notebook files). I went back and forth between them before finally settling on VSCode once they integrated Jupyter Notebook-style cells and output into base VSCode. When I was starting out with Python, I was torn between Spyder (a Python IDE in Matlab style, similar to RStudio) and VSCode. So first trial was a washout but I want to give it another go before giving up.Īlso vscode will be github friendly since github and vscode come from MS !!! I have been meaning to try it on my Linux PC. Truth is first time I used R studio I felt same but familiarity begets comfort I guess in this case.Īnother titbit, I tried to set up vscode for my portable setting of R quickly and it wasn't friendly and so gave up. Update: I taught my nephew some R using R studio and suggested to try vscode.( hardly within months ) and he said the interface is weird and non intuitive.
And of course most examples on internet are based on Rstudio so vscode will have a learning curve If a beginner learns using vscode they may find it easier those of us transitioning may find it difficult.
I know you can write python code within R but vscode is a more general purpose IDE where Rstudio is R specific.
If you are looking at multi language development set up.
0 kommentar(er)
