-
|
I find Cursor to be a superior AI code editing platform to VSCode+Copilot. If WPILib were a pure VS Code extension (or set of extensions), I'd (presumably) be able to develop for FRC inside Cursor. Even if you do not find Cursor compelling, I personally find it really distasteful to have to install and maintain two different VS Code installs, sets of preferences, useful extensions, and so on. Is there any optimism or sense that the problems that previously drove the decision to the current Docker-style approach—"oh just wrap everything up because it's too much work to keep up with XYZ"—might no longer be such a problem? Or that perhaps the benefits of using Cursor, or teaching students to use industry-standard tools instead of a bespoke installer, might be worth returning to a simpler extension-only approach? My words above look inflammatory. My intention is not to belittle what may be a massive undertaking by the great WPILib developers. I have no idea how much work living as an extension only caused. I'm truly not trying to annoy anyone. I simply love the elegance of VS Code and its extensions, and really want programming students to undergo steps that match the industry development practices to the greatest extent possible. |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 1 reply
-
|
Theres nothing stopping you from installing the FRC extension into a normal copy of VS Code from the VSIX. We just generally don't go around stating that, because we don't always test with newer versions of VS Code, and it has broken in the past with a VS Code update. As for shipping Microsoft VS Code, we have to do that in order to have the C++ extension and Java debugging extension work. Those are locked down to only work inside of Microsoft shipped VS Code, and none of the other options provide the reliability or ease of use that we need. |
Beta Was this translation helpful? Give feedback.
-
|
I'm going to mark this as the solution. We're going to keep it a separately installable vsix, and don't plan on doing anything to force it into a specific copy of VS Code. But as for the copy we still, it will continue to be a separately installed copy of Microsoft VS Code. |
Beta Was this translation helpful? Give feedback.
-
you mean “is there a chance that teams would stop struggling with installing an IDE separately from the plugin/environment to get going and spend a lot of needless time and volunteer attention to get going?” no lol |
Beta Was this translation helpful? Give feedback.
Theres nothing stopping you from installing the FRC extension into a normal copy of VS Code from the VSIX. We just generally don't go around stating that, because we don't always test with newer versions of VS Code, and it has broken in the past with a VS Code update.
As for shipping Microsoft VS Code, we have to do that in order to have the C++ extension and Java debugging extension work. Those are locked down to only work inside of Microsoft shipped VS Code, and none of the other options provide the reliability or ease of use that we need.