Hi and thanks for raising these great points! No doubt Rust is currently the darling language of the broad community and especially Microsoft, which has been eyeing memory-safe Rust for all kinds of uses.
No one knows what goes on in the black box of Microsoft management, however, so we have to wait and see what their plans are. You should certainly weigh in on the Developer Community site – Microsoft does a great job answering questions and addressing issues there. In the meantime, here’s what we know now:
Rust
Visual Studio doesn’t yet include official Rust support—but you can install the community-made rust-analyzer.vs extension for features like IntelliSense, Cargo integration, debugging, Clippy/fmt, testing, and more. It’s actively maintained, though not built by Microsoft. For now, many developers gravitate toward Visual Studio Code with the official rust-analyzer extension, which remains the most polished and widely adopted Rust editing experience.
Golang (Go)
There’s currently no official Go support in Visual Studio IDE, and the feature is still under review within Microsoft. If you want to work on console, web, or other Go workloads today, your best experience will be in VS Code with its dedicated Go extension.
Python
Python enjoys mature support in Visual Studio through the Python development workload, including interpreter management, web templating (Flask, Django, Bottle), data science via Anaconda, Cookiecutter templates, and native extensions (C/C++). Visual Studio is already a strong IDE for Python—but there’s indeed an opportunity to deepen tooling for GUI development, mobile frameworks, and AI/ML workflows.
In summary: Rust and Go are better in VS Code for now—Rust has partial IDE support; Go has none—while Python is already well-supported in Visual Studio, with room to grow in specialized domains.
We’ll continue to monitor Microsoft’s roadmap and upcoming feedback items—especially around Rust becoming first-class in Visual Studio, or expanded support scenarios for Python. Thanks again for the thought-provoking post!