---
# System prepended metadata

title: Go Survey draft

---

# Rust Vision Doc: Survey for Go Developers

## Introduction

Rust turns 10 this year and the Rust project is working to understand where Rust is today and get some alignment for where we should be going in the future to *empower everyone to build reliable, efficient software*.

We shared an [initial survey](https://blog.rust-lang.org/2025/04/04/vision-doc-survey/) back in April, but didn't hear much from Go developers - and we'd like to understand your perspective, whether you've used Rust or not.

**Our goals:**
- Build a shared understanding of where Rust is today
- Identify where Rust should be going at a high level
- Learn from developers working in other language ecosystems

**What this is NOT:**
- We're not trying to convince you to use Rust
- We're not looking for specific feature requests or designs
- This is not a comparison or advocacy exercise

We want to understand your work, your experiences with Go, and (if relevant) your thoughts on Rust. Your honest perspective will help us identify both where Rust could improve and where Go's approach may simply be a better fit for certain use cases.

**Privacy:** Your individual responses will not be made public. We may share aggregated themes and anonymized insights in our Vision RFC.

**Time commitment:** This survey should take approximately 10-15 minutes to complete.

---

## Your Work & Experience

### What types of projects or domains do you primarily work on?

* [ ] Network services or cloud computing
* [ ] Embedded development
* [ ] Machine learning or AI
* [ ] Game development
* [ ] CLIs
* [ ] Web
* [ ] Desktop or GUI
* [ ] Other ()

### What languages do you regularly use?

* [ ] Go
* [ ] Rust
* [ ] C
* [ ] C++
* [ ] Python (or similar interpreted languages)
* [ ] Bash (or any other shell language)
* [ ] Java or C#
* [ ] JavaScript/TypeScript
* [ ] Other ()

### How long have you been using Go?

- [ ] Less than 6 months
- [ ] 6 months - 1 year
- [ ] 1-2 years
- [ ] 3-5 years
- [ ] 5+ years
- [ ] I don't use Go.

### Have you used Rust in any capacity?

- [ ] I have never heard of Rust
- [ ] I have read about Rust and am not interested in using it
- [ ] I have read about Rust and am interested in using it
- [ ] I have experimented with Rust (tutorials, small projects)
- [ ] I have used Rust for hobby/side projects
- [ ] I have used Rust professionally

### If you have NOT used Rust, what are the primary reasons?

(Skip this question if you have used Rust)

### If you HAVE used Rust, how would you describe your experience level?

(Skip this question if you have not used Rust)

- [ ] Beginner (working through tutorials, basic syntax)
- [ ] Intermediate (can write working programs, still learning patterns)
- [ ] Advanced (comfortable with ownership, lifetimes, and Rust idioms)
- [ ] Expert (deep understanding)

---

## Working with Go

### What makes Go a good fit for your work?

### For projects where you ultimately chose Go, what factors contributed most in that decision?

### What challenges do you encounter when working in Go?

### What tradeoffs do you accept by using Go?

---

## Cross-Language Perspective (Optional)

**Note:** This section is primarily for those who have some experience with Rust. If you haven't used Rust, feel free to skip.

### If you have used both Go and Rust: What differences stood out to you?

### Are there situations where you would choose Rust over Go, or vice versa? What determines that choice?

---

## Additional Context and Contact Information

### Is there anything else you'd like to share about your experience with Go, Rust, or programming language choices in general?

### Would you be willing to participate in a follow-up interview (~45 minutes) to discuss these topics in more depth?

- [ ] Yes, I'm interested in a follow-up interview
- [ ] Maybe, depending on timing
- [ ] No

**If you answered yes or maybe, please provide your email (or other contact info):**

- Contact info: ()

---

Thank you for taking the time to share your perspective! Your input will help shape Rust's development over the next decade.

If you'd like to learn more about the Rust Vision Doc effort, you can see our [blog post from earlier this year](https://blog.rust-lang.org/2025/04/04/vision-doc-survey/) or watch our [RustConf 2025 talk](https://www.youtube.com/watch?v=f0N3m8U0b2k).
