Basically R studio/Spyder + Cursor built on the Code - OSS behind VSCode.
Potentially very exciting. The early builds a year or two ago that I tried were too buggy to replace R Studio, but a tight integration of good data tools, a good IDE, and modern AI coding assistants is going to be very powerful if posit nails this.
i wish they had a more exhaustive list of all the features they offer beyond vscode or cursor, otherwise it's hard to evaluate what exactly it brings to the table.
The common answer to "why do you fork instead of building an extension" is "these are not possible with VS Code extensions". Is this true? Or is it easier to monetize when it is a fork?
I've been using for over 4 months and I think it's great - both Python and R. Plenty of DS features that make VS Code feel more competent as data exploration tool.
For R+RStudio users, any opinions on the switch? Assistant seems to be the big departure, trying to work out if worth losing keyboard shortcut muscle memory for
This has been in beta for over a year, and unfortunately R users mostly seem to hold onto RStudio with a religious conviction so I haven’t really seen much adoption among the target demographic in my circles.
I have a feeling that hardcore data scientists will continue to use RStudio because of the huge ecosystem there, while data engineers will continue to use VSCode which is, at least for me, good enough with a few extensions that let me run notebooks and data visualizations when I need to do data work. In other words, I'm not sure if there's a niche here.
The only thing from keeping me from transitioning from RStudio to Positron is the lack of inline plots in Quarto files.
Is there any plan or consideration for this to be implemented? It's a wildly important aspect of mine and many other RStudio user's analysis pipelines.
I switched to Positron a few months ago and have mostly found it seamless.
I'm an academic bioinformatician/data scientist and I mostly use R to do my data visualization and table wrangling. I use quarto documents. Before positron I used RStudio as well as VSCode with lots of extensions to add R functionality there.
My main gripes with Positron are no inline plots underneath code chunks, and some bugs where sending code to the console from code chunks occasionally stops working until restarting the program, and View() occasionally stops working. But the better file explorer, integration with Claude Code, and access to most of my VSCode extensions make it worth it for me.
As an R user coming from RStudio and VSCode, Positron's file explorer and Claude integration are tempting. The lack of inline plots and occasional console bugs are concerning though. The core services API approach is smart for extensibility!
1. Position has been on hacker news 2 months ago.
2. I don't think there are features in position that is not possible through a vscode extension.
3. I want `ark` to be able to be used as a standard LSP.
4. Position has absurb experience when coming to ai. It has to use 2 difference system to do tab completion and edit/ask/agent. The experience is also not good --- I mean, even not good as copilot.
22 comments
[ 3.3 ms ] story [ 48.2 ms ] threadDataspell is IDE.
Potentially very exciting. The early builds a year or two ago that I tried were too buggy to replace R Studio, but a tight integration of good data tools, a good IDE, and modern AI coding assistants is going to be very powerful if posit nails this.
These guys' PR is trying too hard.
(reference: Ju in Jupyter is Julia)
Is there any plan or consideration for this to be implemented? It's a wildly important aspect of mine and many other RStudio user's analysis pipelines.
I'm an academic bioinformatician/data scientist and I mostly use R to do my data visualization and table wrangling. I use quarto documents. Before positron I used RStudio as well as VSCode with lots of extensions to add R functionality there.
My main gripes with Positron are no inline plots underneath code chunks, and some bugs where sending code to the console from code chunks occasionally stops working until restarting the program, and View() occasionally stops working. But the better file explorer, integration with Claude Code, and access to most of my VSCode extensions make it worth it for me.